JayPe•14mo ago

Dev container does not work anymore

When trying to execute the dev container to modify the code, I have the following error :

29 Replies

FFO•14mo ago

Hm, how did you start the container?

JayPeOP•14mo ago

by using rebuild and reopen container

FFO•14mo ago

Ok, let me quickly try to reproduce... I guess from main?

JayPeOP•14mo ago

I tried to remove all dev images / prune all Yes from main with a little bit of specific code, but that didn't change for 3 months I can try without any specific code tried to restart docker servoce

FFO•14mo ago

Give me a few minutes to spin one fresh up.

JayPeOP•14mo ago

tried to reboot my laptop

[2024-10-01T11:26:49.862Z] Client: Docker Engine - Community
 Version:           27.2.1
 API version:       1.47
 Go version:        go1.22.7
 Git commit:        9e34c9b
 Built:             Fri Sep  6 12:08:10 2024
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
[2024-10-01T11:26:49.862Z]   Version:          27.2.1
  API version:      1.47 (minimum version 1.24)
  Go version:       go1.22.7
  Git commit:       8b539b8
  Built:            Fri Sep  6 12:08:10 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.22
  GitCommit:        7f7fdf5fed64eb6a7caf99b3e12efcf9d60e311c
 runc:
  Version:          1.1.14
  GitCommit:        v1.1.14-0-g2c9f560
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

[2024-10-01T11:26:49.862Z] Client: Docker Engine - Community
 Version:           27.2.1
 API version:       1.47
 Go version:        go1.22.7
 Git commit:        9e34c9b
 Built:             Fri Sep  6 12:08:10 2024
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Engine - Community
 Engine:
[2024-10-01T11:26:49.862Z]   Version:          27.2.1
  API version:      1.47 (minimum version 1.24)
  Go version:       go1.22.7
  Git commit:       8b539b8
  Built:            Fri Sep  6 12:08:10 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.22
  GitCommit:        7f7fdf5fed64eb6a7caf99b3e12efcf9d60e311c
 runc:
  Version:          1.1.14
  GitCommit:        v1.1.14-0-g2c9f560
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

FFO•14mo ago

with me, it started successfully

JayPeOP•14mo ago

which OS ? which docker version ?

FFO•14mo ago

Darwin ffo-macbook.local 24.1.0 Darwin Kernel Version 24.1.0: Tue Sep 17 07:46:59 PDT 2024; root:xnu-11215.40.59~38/RELEASE_ARM64_T6000 arm64

JayPeOP•14mo ago

did you remove everything ? containers / images / docker system prune -a ?

FFO•14mo ago

Docker version 27.2.0, build 3ab4256 It was a clean machine, newly installed docker, so nothing cached here

JayPeOP•14mo ago

ok ok thanks for the test

FFO•14mo ago

have you tried docker sytem prune -a? (that will delete other containers and images as well, so be cautious)

JayPeOP•14mo ago

Yes yes already did it It works on my colleague laptop (windows + WSL) on my side, ubuntu, it does not work but the error is not really understandable

FFO•14mo ago

Yeah that error is super cryptic It sounds a little like that the devcontainer misses a file when starting. Have you tried reinstalling the devcontainer extension?

JayPeOP•14mo ago

Nop, I'll try it thank you 🙂 If I found a solution I 'll add it here

JayPeOP•14mo ago

when uninstall install again dev container extension, I see the main error

JayPeOP•14mo ago

This is the network mode ! by removing it takes the bridge, and it can goes outside. by keeping it, it's internal docker network, and it can't go outside

FFO•14mo ago

Hm interesting that this fails. I mean its a dev container, we could remove that flag. You wana do a PR? Happy to review

JayPeOP•14mo ago

BUT, it's maybe due to my docker configuration according to my ubuntu host. As it works on your host and my colleague host

FFO•14mo ago

Could be, true. I wonder a little bit, because if we take out that flag... how does zitadel communicate with the DB? It lacks port exposure 🤷‍♂️

JayPeOP•14mo ago

Indeed if you do not specify any networks, then both containers will use the existing bridge one, so they'll be able to communicate

FFO•14mo ago

It just tried it and it works on a mac as well Does it also work on WSL2?

JayPeOP•14mo ago

I'll let you know ASAP it's ok for WSL too

FFO•14mo ago

Perfect, do you wana create a PR, or should I?

JayPeOP•14mo ago

I can do it, but next week

FFO•14mo ago

Thanks!

Dev container does not work anymore

Did you find this page helpful?