docker daemon does not seem to be started

[guiyomh]

Hello. Thanks for your work (I use your features every day!).

But since today I have a problem with the docker-in-docker feature.
Strangely, the docker service does not seem to run.

I rebuilt my dev env. And when I do: devcontainer features test --features vim --base-image mcr.microsoft.com/devcontainers/base:ubuntu .

I have this output

┌ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ┐
|    dev container 'features' |   
│           v0.14.2           │
└ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ┘

>  baseImage:         mcr.microsoft.com/devcontainers/base:ubuntu
>  Target Folder:     /workspaces/features
>  features:          vim
>  workspaceFolder:   /tmp/vsch/container-features-test/1663354490504

⏳ Building test container...

[2 ms] @devcontainers/cli 0.14.2.
[-] Failed to launch container:

Command failed: docker ps -q -a --filter label=devcontainer.local_folder=/tmp/vsch/container-features-test/1663354490504
error: Recipe `test` failed on line 17 with exit code 1

After some research, I try to make docker image ls and I have this error:

Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

I don't know if it's my host machine or the feature that no longer works. Because last week it was working fine!
If you want to test the case, here is my project https://github.com/guiyomh/features.

start the devcontainer and try to run just test vim

[samruddhikhandale]

Glad to know that you are using Features and it's cool to see that you've self published some Features as well. ✨ 👏

I tried to reproduce the issue with latest Remote Containers and I was able to execute the test without any issues. Also, the individual docker-in-docker Feature works fine for me.

devcontainer features test --features vim --base-image mcr.microsoft.com/devcontainers/base:ubuntu .

My Machine details (Mac OS)

• VS Code - v1.71.1
• Remote Containers - v0.251.0
• Docker - 4.9.1

@guiyomh Could you run the cmd with --log-level trace and paste the logs? Interested to see where it is failing for you.
It looks like the issue could be with some configuration on your host machine.

Also, docker is running for me, sudo ps aux | grep dockerd and docker image ls works fine too.

Tip: Looks like the /test/vim folder does not contain scenarios and you probably want to test the /test/vim/test.sh file, then you could add the --skip-scenarios flag to the above command.

[guiyomh]

@samruddhikhandale

Of course, here the log:

devcontainer features test --log-level trace --features vim --base-image mcr.microsoft.com/devcontainers/base:ubuntu .

┌ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ┐
|    dev container 'features' |   
│           v0.14.2           │
└ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ┘

>  baseImage:         mcr.microsoft.com/devcontainers/base:ubuntu
>  Target Folder:     /workspaces/features
>  features:          vim
[5 ms] Start: Run: docker buildx version
[150 ms] Stop (145 ms): Run: docker buildx version
>  workspaceFolder:   /tmp/vsch/container-features-test/1663572873119

⏳ Building test container...

[3 ms] @devcontainers/cli 0.14.2.
[3 ms] Start: Run: docker buildx version
[147 ms] Stop (144 ms): Run: docker buildx version
[147 ms] Start: Resolving Remote
[159 ms] Start: Run: git rev-parse --show-cdup
[165 ms] Stop (6 ms): Run: git rev-parse --show-cdup
[168 ms] Start: Run: docker ps -q -a --filter label=devcontainer.local_folder=/tmp/vsch/container-features-test/1663572873119
[216 ms] Stop (48 ms): Run: docker ps -q -a --filter label=devcontainer.local_folder=/tmp/vsch/container-features-test/1663572873119
[-] Failed to launch container:

Command failed: docker ps -q -a --filter label=devcontainer.local_folder=/tmp/vsch/container-features-test/1663572873119
error: Recipe `test` failed on line 18 with exit code 1

My machine (Mac OS):

VS Code - v1.70.2
Remote Containers - v0.245.2
Docker - 20.10.14

[samruddhikhandale]

Thanks! Looking at the versions of VS Code and Remote Containers, it looks like you are on quite older ones. Could it be possible to update both to (stable) latest and test?

[samruddhikhandale]

Closing this issue due to inactivity. Feel free to re-open if the issue resurfaces.

[guiyomh]

oh thx @samruddhikhandale, I haven't seen your response. I haven't solved the pb yet, but I think it's related to my host environment.