Switching to 16 core codespaces machine type results in loss of docker daemon #43317
Unanswered
nick-youngblut
asked this question in
Codespaces
Replies: 3 comments
-
I've been unable to reproduce this even with your devcontainer. Do you have a repo with a repro of this available? I would also point out your devcontainer.json has two entries for |
Beta Was this translation helpful? Give feedback.
0 replies
-
I also haven't been able to reproduce the issue. The issue happened twice (so, reproducible), but now it works correctly 🤷 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Bug
Body
If is use a 2 or 4 core codespaces machine type, docker works correctly (e.g.,
docker image ls
), but if I change the container to the16 core, 32 Gb RAM, 128 Gb storage
option, then I get the following error when trying to run docker:$ docker image ls Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
If I try to start the docker daemon, I get the following:
I have tried rebuilding the container, and I have attempted this switch form 2 (or 4) core machines to the 16 core machine multiple times. Each time, I get the
docker daemon
error.Has anyone else encountered this issue?
I need docker and a high memory machine for my development needs, so due to this issue, I have to find an alternative for codespaces (e.g., gitpod).
My
devcontainer.json
:Beta Was this translation helpful? Give feedback.
All reactions