microsoft / microsoft/vscode-remote-release
Failure to start devcontainer in podman on a remote box
@chrmarti is already working on this.
Since Jun 20, 2025.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
- VSCode Version: 1.100.2
- Local OS Version: MacOs Sequoia 15.4.1
- Remote OS Version: RedHat EL 9
- Remote Extension/Connection Type: Dev Containers/WSL/Remote - Tunnels/VS Code Server: trying to run dev container on a remote host over Remote-SSH
- Logs:
[446 ms] Dev Containers 0.417.0 over Remote - SSH 0.120.0 in VS Code 1.100.2 (848b80aeb52026648a8ff9f7c45a9b0a80641e2e).
…
[5963 ms] Start: Run: podman version --format {{json .}}
[6423 ms] {"Client":{"APIVersion":"5.2.2","Version":"5.2.2","GoVersion":"go1.22.7 (Red Hat 1.22.7-2.el9_5)","GitCommit":"","BuiltTime":"Fri Nov 15 08:49:31 2024","Built":1731660571,"OsArch":"linux/amd64","Os":"linux"}}
[6426 ms] Stop (463 ms): Run: podman version --format {{json .}}
[6436 ms] Initializing configuration support...
[6440 ms] Internal initialization of dev container support package...
[20907 ms] TypeError: Cannot read properties of undefined (reading 'toString')
at HF (/Users/dmitanta/.vscode/extensions/ms-vscode-remote.remote-containers-0.417.0/dist/extension/extension.js:325:44579)
Steps to Reproduce:
- Setup Remote-SSH to a remote linux machine. The remote machine has podman installed.
- Set dev.containers.dockerPath=podman
- Open a remote folder
- Run "Dev Containers > Reopen in devcontainer" command
Does this issue occur when you try this locally?: Cannot verify, no local docker/podman installed.
Does this issue occur when you try this locally and all extensions are disabled?: Cannot verify
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.