Cannot find temporary feature layer in podman
@chrmarti is already working on this.
Since Jul 21, 2025.
Assessment
This issue has not been assessed yet.
Description
Version: 1.102.1 (user setup)
Commit: 7adae6a56e34cb64d08899664b814cf620465925
Date: 2025-07-15T16:41:17.147Z
Electron: 35.6.0
ElectronBuildId: 11847422
Chromium: 134.0.6998.205
Node.js: 22.15.1
V8: 13.4.114.21-electron.0
OS: Windows_NT x64 10.0.26100
-
Remote OS Version: Fedora 42 (official image)
-
Remote Extension/Connection Type: WSL
-
Logs:
remoteContainers-2025-07-21T02-31-38.913Z.log
I'm trying to use podman, and have been hitting a number of issues when trying to use podman-compose. This report is due to one of my attempted workarounds.
Steps to Reproduce:
- Install Fedora on WSL with
wsl --install FedoraLinux-42, and finish setup - Install podman and wget with
sudo dnf install podman podman-compose wget. - Change settings necessary to use podman with devcontainers:
"dev.containers.dockerPath": "podman""dev.containers.dockerComposePath": "podman compose""dev.containers.executeInWSLDistro": "FedoraLinux-42"
- Put the following repo contents (essentially a stripped-down C#/SQL Server setup) into a directory in the WSL distro: .devcontainer.zip
- Open with
code <wherever>, and follow the prompt to open the container.VSCode attempts to build the devcontainer, but hangs because podman tries to ask where it should be trying to pull the temp working image for feature install from. No interaction is available in the terminal log, and in any case the image isn't from a registry so would fail anyways.
Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
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.
More from microsoft/vscode-remote-release
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/vscode-remote-release#11650 ·
-
ssh
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/vscode-remote-release#11583 ·
-
ssh
Difficulty 4/5 3-5 days Newbie friendliness 38/100
microsoft/vscode-remote-release#11861 ·
-
microsoft/vscode-remote-release#11860 · 1 comment · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
microsoft/vscode-remote-release#11859 ·