microsoft / microsoft/vscode-remote-release
Can't use Podman Compose with features with rootless podman
Open
@chrmarti is already working on this.
Since Jul 22, 2025.
bug
containers
podman
rootless
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
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 Extension/Connection Type: Dev Containers, extension version 0.424.0
- Logs: remoteContainers-2025-07-22T02-56-32.818Z.log
I'm attempting to use podman desktop on Windows (instead of docker desktop), and would prefer to use rootless podman. Unfortunately, it won't start podman compose configurations of any sort if the devcontainer contains a feature. Single-container devcontainers work fine, but the process of building/launching a compose version breaks with a feature breaks.
Steps to Reproduce:
- Install Podman Desktop, and set rootless mode with
podman machine set --rootful=false(you may have to stop/restart the machine) - Attempt to create a devcontainer definition that uses a compose file. The default c# and Azure SQL one does this, but even a stripped-down one with only a single container reproduces the error. You can create a working container definition and then substitute these contents: .devcontainer.zip
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
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.