microsoft / microsoft/vscode-remote-release
Bootstrap container not compatible with podman (desktop).
@chrmarti is already working on this.
Since Oct 14, 2024.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Version: 1.94.2 (user setup)
Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427
Date: 2024-10-09T16:08:44.566Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631
Remote Extension/Connection Type: WSL
I'm attempting to set up podman desktop, but unfortunately the boostrapping container used when cloning into a volume uses docker, not podman. The problem with this is that multiple of the options that podman supports are errors for the docker cli. In particular the option --userns keep-id causes an error for the docker cli contained in the bootstrap container (and the recovery container).
Note that this option is generally required for id-mapping to work correctly on rootless-mode podman when host-mounting resources.
Steps to Reproduce:
- Install podman-desktop (perhaps via winget on Windows:
winget install --id RedHat.Podman-Desktop), ensure that you install/run in rootless mode. - Configure
dev.containers.dockerComposePathtopodman composeanddev.containers.dockerPathtopodman - Clone in a devcontainer (creating a new devcontainer appears to be broken). A working example for this is the repository
https://github.com/ephemeris-rust/ephemeris
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.