You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One thing that might be relevant is that I set the DOCKER_UNIX_SOCKET_PATH environment variable with /var/run/docker.sock instead of /Users/lucassantos/Library/Containers/com.docker.docker/Data/docker.raw.sock. When the env variable is set with the last one, sometimes the API can't even create the code-runner container.
I don't know if the CPU architecture or OS are problems, but setup is a M1 MacBook Pro with macOS Sonoma Beta 3.
Activity
[-]Unable to attach to a container[/-][+]Unable to attach to a glot-image container[/+]lslm commentedon Jul 14, 2023
I think the problem is macOS Docker Desktop. I managed to make the code execution API work by using Colima, instead of Docker Desktop. I found the solution here: https://apple.stackexchange.com/questions/373888/how-do-i-start-the-docker-daemon-on-macos