ARM pipelines runner stops working if Docker moved to SSD

[Michael Friedman]

We set up a self-hosted ARM runner for our Bitbucket Pipeline on an NVidia Jetson Xavier AGX. The runner worked well, but there wasn't much space left on the drive that Docker was on, so we installed an SSD and moved Docker's data root directory onto there. Unfortunately, that meant the Bitbucket Pipeline stopped working, with no error message given.

The attached photos show the results of running the exact same commit's Pipeline on the main Xavier drive, vs. on the SSD, using the identical runner. Both find the runner, but one just hangs up after about a minute (logs of the runner container also attached as a photo, ending with "Completing step with result Result{status=FAILED, error=None}"), the other processes as usual - also seems to divvy things up differently between the runner and build steps.

`docker system info` is identical for both setups, except for the "Docker Root Dir" field.

[John Rhodes]

I've had this sort of issue before, and sometimes it can be related to how the drive is set up. I found that learning how to format SSD correctly helped solve some similar problems. It could be worth looking into partitioning and formatting specifics for SSDs on Windows. This tool’s features like secure erase workflows and drive read verification might just do the trick for your setup.

[Michael Friedman]

[Michael Friedman]

^^These are the images, forgot to press Insert on main post

[Lars Martin Sandvik Aas]

Hi Michael.

Did you find a solution to this?