Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bootstrap container not compatible with podman (desktop). #10386

Open
Clockwork-Muse opened this issue Oct 14, 2024 · 0 comments
Open

Bootstrap container not compatible with podman (desktop). #10386

Clockwork-Muse opened this issue Oct 14, 2024 · 0 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug containers Issue in vscode-remote containers

Comments

@Clockwork-Muse
Copy link

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:

  1. Install podman-desktop (perhaps via winget on Windows: winget install --id RedHat.Podman-Desktop), ensure that you install/run in rootless mode.
  2. Configure dev.containers.dockerComposePath to podman compose and dev.containers.dockerPath to podman
  3. Clone in a devcontainer (creating a new devcontainer appears to be broken). A working example for this is the repository https:/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

@vs-code-engineering vs-code-engineering bot added the containers Issue in vscode-remote containers label Oct 14, 2024
@joshspicer joshspicer added the bug Issue identified by VS Code Team member as probable bug label Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug containers Issue in vscode-remote containers
Projects
None yet
Development

No branches or pull requests

3 participants