Can't use DevContainer after updating VSCode Dev Containers from `0.394.0` to `0.397.0`

[eitsupi]

• VSCode Version: 1.97.0
• Local OS Version: Windows 11
• Remote OS Version: Ubuntu
• Remote Extension/Connection Type: Dev Container
• Logs:

[81 ms] Dev Containers 0.397.0 in VS Code 1.97.0 (33fc5a94a3f99ebe7087e8fe79fbe1d37a251016).
[80 ms] Start: Run: wsl -d ubuntu-lts -e wslpath -u \\wsl.localhost\ubuntu-lts\home\username\works\proj-name
[394 ms] Start: リモートの解決
[433 ms] Start: Run: wsl -d ubuntu-lts -e wslpath -u \\wsl.localhost\ubuntu-lts\home\username\works\proj-name
[702 ms] Start: Run: wsl -d ubuntu-lts -e /bin/sh -c cd '/home/username/works/proj-name' && /bin/sh
[714 ms] Start: Run in host: id -un
[835 ms] username
[835 ms] 
[836 ms] Start: Run in host:  (command -v getent >/dev/null 2>&1 && getent passwd 'username' || grep -E '^username|^[^:]*:[^:]*:username:' /etc/passwd || true)
[842 ms] Start: Run in host: echo ~
[844 ms] /home/username
[845 ms] 
[846 ms] Start: Run in host: test -f '/home/username/.vscode-server/cli/servers/Stable-33fc5a94a3f99ebe7087e8fe79fbe1d37a251016/server/node'
[848 ms] 
[848 ms] 
[848 ms] Exit code 1
[849 ms] Start: Run in host: test -f '/home/username/.vscode/cli/servers/Stable-33fc5a94a3f99ebe7087e8fe79fbe1d37a251016/server/node'
[851 ms] 
[851 ms] 
[851 ms] Exit code 1
[852 ms] Start: Run in host: test -f '/home/username/.vscode-server/bin/33fc5a94a3f99ebe7087e8fe79fbe1d37a251016/node'
[853 ms] 
[853 ms] 
[854 ms] Start: Run in host: test -f '/home/username/.vscode-server/bin/33fc5a94a3f99ebe7087e8fe79fbe1d37a251016/node_modules/node-pty/package.json'
[858 ms] 
[858 ms] 
[859 ms] Start: Run in host: test -f '/home/username/.vscode-remote-containers/dist/vscode-remote-containers-server-0.397.0.js'
[861 ms] 
[861 ms] 
[868 ms] userEnvProbe: loginInteractiveShell (default)
[868 ms] userEnvProbe: not found in cache
[869 ms] userEnvProbe shell: /usr/bin/bash
[941 ms] Error reading shell environment.
[942 ms] Error: stream ended with:0 but wanted:9
        at l (c:\Users\username\.vscode\extensions\ms-vscode-remote.remote-containers-0.397.0\dist\extension\extension.js:27:22149)
        at c:\Users\username\.vscode\extensions\ms-vscode-remote.remote-containers-0.397.0\dist\extension\extension.js:27:22330
        at s (c:\Users\username\.vscode\extensions\ms-vscode-remote.remote-containers-0.397.0\dist\extension\extension.js:30:5371)
        at Socket.<anonymous> (c:\Users\username\.vscode\extensions\ms-vscode-remote.remote-containers-0.397.0\dist\extension\extension.js:30:5541)
        at Socket.emit (node:events:530:35)
        at endReadableNT (node:internal/streams/readable:1698:12)
        at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[952 ms] Error: stream is closed
        at c:\Users\username\.vscode\extensions\ms-vscode-remote.remote-containers-0.397.0\dist\extension\extension.js:30:3813
        at o (c:\Users\username\.vscode\extensions\ms-vscode-remote.remote-containers-0.397.0\dist\extension\extension.js:30:1926)
        at MR.e.<computed> [as setBaseEnv] (c:\Users\username\.vscode\extensions\ms-vscode-remote.remote-containers-0.397.0\dist\extension\extension.js:30:1684)
        at c:\Users\username\.vscode\extensions\ms-vscode-remote.remote-containers-0.397.0\dist\extension\extension.js:99:686
        at new Promise (<anonymous>)
        at Object.setBaseEnv (c:\Users\username\.vscode\extensions\ms-vscode-remote.remote-containers-0.397.0\dist\extension\extension.js:99:655)
        at vb (c:\Users\username\.vscode\extensions\ms-vscode-remote.remote-containers-0.397.0\dist\extension\extension.js:124:3590)
        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
        at async UEe (c:\Users\username\.vscode\extensions\ms-vscode-remote.remote-containers-0.397.0\dist\extension\extension.js:342:23535)
        at async c:\Users\username\.vscode\extensions\ms-vscode-remote.remote-containers-0.397.0\dist\extension\extension.js:342:18295
[955 ms] Host server terminated (code: 0, signal: null).
[955 ms] Host server terminated early. Not reconnecting.

Steps to Reproduce:

1. Select the reopen in container command

Does this issue occur when you try this locally?: NA
Does this issue occur when you try this locally and all extensions are disabled?: NA

[joshspicer]

Does the issue reproduce on the last stable Dev Containers release (0.394.0)?

[eitsupi]

Does the issue reproduce on the last stable Dev Containers release (0.394.0)?

Thanks for your suggestion. It seems working with 0.394.0.

[joshspicer]

Thank you for checking, @eitsupi

[oleg-nenashev]

Confirmed on 0.401.0 and Debian as a target
In my case, it seems to be something linked to the DinD feature and privileged mode, because the same configuration runs smoothly without the feature and the flags.

See testcontainers/testcontainers-native#43 and testcontainers/testcontainers-native@c8da752 specifically for my container configuration

[chrmarti]

@eitsupi Could you share your devcontainer.json (and Dockerfile if any)?

@oleg-nenashev Please append the Dev Containers log from when this happens. (F1 > Dev Containers: Show Container Log)

Regarding Docker-in-Docker the following config works for me:

{
	"image": "debian:bookworm-20250317",
	"features": {
		"ghcr.io/devcontainers/features/docker-in-docker:2.12.1": {
			"version": "latest",
			"moby": true
		}
	}
}

[eitsupi]

@eitsupi Could you share your devcontainer.json (and Dockerfile if any)?

Perhaps this repository.
https://github.com/eitsupi/neo-r-polars

[oleg-nenashev]

@chrmarti I will capture it today or tomorrow once I get access to the Windows machine again.
I also need to check whether the overrideCommand or the Docker engine / WSL bridge are the culprit.

[chrmarti]

@eitsupi Your log shows it failing while trying to read the env variables from bash. Is there anything special about ~/.bashrc, ~/.bash_profile or ~/.profile in your ubuntu-lts distro?

[eitsupi]

Is there anything special about ~/.bashrc, ~/.bash_profile or ~/.profile in your ubuntu-lts distro?

I have rarely edited those files.
The only things I have done are what is described in the comments below and the homebrew settings.
#6032 (comment)

[chrmarti]

What do you get for running bash -lic 'cat /proc/self/environ' | tr '\0' '\n' in WSL? (Check the content for things that shouldn't be public before posting.)