bramankp

``` 2023-10-17 15:18:00.200 [info] [127.0.0.1][84130da3][ExtensionHostConnection] New connection established. 2023-10-17 15:18:00.246 [info] [127.0.0.1][84130da3][ExtensionHostConnection] Launched Extension Host Process. 2023-10-17 15:18:05.634 [info] [127.0.0.1][1057d43e][ManagementConnection] The client has reconnected. 2023-10-17 15:18:11.164 [info] [127.0.0.1][1057d43e][ManagementConnection] The client...

3.4.2 on Ubuntu 20.04 3.4.4 on Ubuntu 22.04 I mean it *could* be a podman issue but the key here is figuring out if it is (or if it's reproducible)...

[devcontainerlog.txt](https://github.com/microsoft/vscode-remote-release/files/13648212/devcontainerlog.txt)

Adding a note that Ubuntu 24.04 LTS seems to work fine. So I suggest everyone avoid that middle step-child of 22.04 if they run into this problem and can use...

Currently using 0.417.0 of that extension (and updated to 1.101.0 of VSC). No change in behavior. I also did just try ``` Dev Containers 0.418.0 in VS Code 1.101.0 (dfaf44141ea9deb3b4096f7cd6d24e00c147a4b1)....

There's definitely something funky going on. I created a minimal test project and the same dev container builds and runs just fine. When I try and build the dev container...

[devcon-failure.txt](https://github.com/user-attachments/files/20794746/devcon-failure.txt) [devcon-success.txt](https://github.com/user-attachments/files/20794745/devcon-success.txt) Both seem to start the same way. At about 4100ms they both run `Running Dev Containers CLI: up --docker-path podman --container-session-data-folder` using "user" 1002 in the command path....

Interesting ... Just out of curiosity I went and removed all instances of previous dev containers using that image and then re-opened the project (which triggered rebuilding the container again)....

Just tested it with someone else (who originally reported the problem) and clearing out all the old dev containers using that image allows all new ones to build successfully. So...