I’m doing some building of a complex Linux project in a --platform linux/amd64 container on macOS 15.4.1 on both an M2 Mac mini and an M4 Mac mini, and have experienced 2 problems.
- After a few builds on either device I was suddenly receiving return code 2 / errors from the build script when
touch <path-to-some-existing-file>ran. Rebooting Docker didn’t solve the issue, but manually killing the docker/Library/PrivilegedHelperTools/com.docker.vmnetdprocess did. This seems like the virtual file-system overlays were having trouble, either with timing (sometimes the touched-file was just created before touch). Restarting the complete build would proceed to the next Makefile instruction to touch and fail again. After completely restarting docker, things proceeded for a bit, and then Docker wanted to update. This leads to… - Now with Docker 4.41.2 (191736), the touch problems are gone, but the system will simply hang after a few minutes of execution. The Docker desktop isn’t complaining, but the build has clearly hung. If I stop the build with CTRL+C and attempt to restart it, the CLI complains:
docker: request returned 500 Internal Server Error for API route and version http://%2FUsers%2Fnatbro%2F.docker%2Frun%2Fdocker.sock/_ping, check if the server supports the requested API version. It will allow the build to continue if I again manually kill the com.docker.vmnetd process, but just stopping and starting the Docker desktop tool does not resolve the issue.
Basically dead in the water now trying to build anything. Any clues or thoughts on resolving this?