Cannot find temporary feature layer in podman

Open
#11,102 0 comments 0 reactions 1 assignee View on GitHub

@chrmarti is already working on this.

Since Jul 21, 2025.

Assessment

This issue has not been assessed yet.

Description

bug containers podman

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:

  1. Install Fedora on WSL with wsl --install FedoraLinux-42, and finish setup
  2. Install podman and wget with sudo dnf install podman podman-compose wget.
  3. Change settings necessary to use podman with devcontainers:
    • "dev.containers.dockerPath": "podman"
    • "dev.containers.dockerComposePath": "podman compose"
    • "dev.containers.executeInWSLDistro": "FedoraLinux-42"
  4. Put the following repo contents (essentially a stripped-down C#/SQL Server setup) into a directory in the WSL distro: .devcontainer.zip
  5. 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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode-remote-release

All issues in microsoft/vscode-remote-release

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.