Docker stops responding on MacOS, error on Arch Linux while building image.
OS: MacOS Sonoma 14.4.1 and Arch Linux
App version:
Cloud integration: v1.0.35+desktop.11
Version: 25.0.3
API version: 1.44
Go version: go1.21.6
Git commit: 4debf41
Built: Tue Feb 6 21:13:26 2024
OS/Arch: darwin/arm64
Context: desktop-linux
Steps to reproduce:
git clone https://github.com/demensdeum/Masonry-AR-Docker.git
cd Masonry-AR-Docker
docker buildx build .
wait some time
stuck at âCXX Magick++/lib/libMagick___7_Q16HDRI_la-TypeMetric.loâ
docker ps not responding
docker images not responding
If I remove ImageMagick build from Dockerfile and move it to terminal, then ImageMagick build ends with error: ERRO[0033] error waiting for container: unexpected EOF
and after that docker ps, docker images did not respond
You mean Docker CE v25.0.0 in Docker Desktop for Mac? Because as far as I know, the latest version on macOS is Docker Desktop 4.28 which has Docker CE 25.0.3 in it. but docker ps not responding doesnât seem to be related.
Regarding the error on macOS, âwaiting for container: unexpecteed EOFâ could be that the API server canât respond properly because the build requires too much resources. That would explain why docker ps canât respond either. Did you try to watch the bottom of the Docker Desktop window while the build runs to see the used resources? You could also optimize your Dockerfile as this doing an upgrade like this is highly discouraged
It is not a vitual machine. Install what you need and donât touch dependencies you donât unless you know about a serious security risk. Otherwise you can actually introduce new security holes or in some cases you can upgrade almost every package which just makes your image much bigger. I could mention more problems, but this topic is not about making a perfect Dockerfile so I wonât do it.
How does that work? Can you share the command? macOS doesnâT support containers, so you need the Desktop. Did you install the Docker CE 26.0.0 clint only?
That is the client. It can be useful when you donât want to run Docker on your machine just connect to a remote machine, but the client comes with Docker Desktop. If you want to use brew, brew install docker-desktop should work probably. Since this is not the officially ecommended way, I always forget A different client could cause hanging docker ps, but then it would never work not just after trying to build an image, so the problem will be on the Docker Daemon side in the virtual machine. Just to avoid other problems caused by the client, I recommend deleting the âdockerâ brew package.
This does not work without colima, and colima is âcontainer runtimes on macOSâ, I can assume that they run linux in vm, and then docker on the top of this linux-vm.
I got original problem without colima, or other client, just vanilla Docker Desktop.
You mean the docker command from brew? Yes colima runs a virtual machine, but the client is just a client. It could work with Docker Desktop or any daemon since the contexts are configured in $HOME/.docker. I ran brew install docker and since I already had the client from Docker Desktop, brew didnât replace my client. It was only kept in /opt/homebrew. I donât know what Docker Desktp would do if it is installed after the other client.