-
Notifications
You must be signed in to change notification settings - Fork 319
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
devcontainers Podman 5.3.1 WSL2 windows 11 #10586
Comments
Any news on this? |
I see you've used the Remote - SSH template. I'll add the appropriate dev container tags and assignees |
From your log, that suggests to me that maybe your version of podman is not compatible with the workaround in the docs, or docker is being used in place? (I'm not sure if
What happens if you run
And use that |
The container is started with Docker from within a temporary container that mounts the Docker volume with the repository. That temporary container does not have Podman installed, but will try to connect to the socket path you have configured. Maybe try without |
It did work and proceeded sucessfully, not running in wsl. |
I made it match previously..
|
So the dev container boots, as we use gpg for signing our commits it's crucial these are linked to the container. The "connection" to my local vault seems unstable. First I forgot to start my local Kleopratra which starts the backing service on windows, since I was testing if the container could start at all. The output I got was this (not surprisingly): log
terminal output
Immediately after this I started Kleopratra and where surprised by the output:
I then wanted to check my public keys : Nothing was output, which is correct. I then went back to check my secret keys again and nothing was output and no info in logs:
Should I create a new issue for this or continue here? |
Let's open a new issue to make it easier to follow each problem. Thanks. This issue can be closed then? |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
Is there an existing issue for this bug?
Required Troubleshooting Steps
remote.SSH.useLocalServer
setting[Optional] Diagnose with Copilot
I did not ask the @remote-ssh participant for help
In step 2 of the troubleshooting wiki, what was the result of running the generated SSH command verbatim outside of VS Code?
I did not try step 2 of the troubleshooting steps
Remote-SSH Log
Remote-SSH Log
Expected Behavior
Podman called, container built and a happy world.
Actual Behavior
Something calls docker which then complains about "--userns: invalid USER mode". I have followed this https://code.visualstudio.com/remote/advancedcontainers/docker-options#_podman
Steps To Reproduce
blank win 11 machine
.wslconfig:
setup git
install podman
install vscode
vscode add devcontainers:
"dev.containers.cacheVolume": false
"dev.containers.copyGitConfig": true
"dev.containers.dockerPath": "podman"
"dev.containers.dockerSocketPath": "/run/user/1000/podman/podman.sock"
"dev.containers.executeInWSL": false
"dev.containers.executeInWSLDistro": "podman-machine-default"
"dev.containers.forwardWSLServices": true
"dev.containers.mountWaylandSocket": true
have repo with.devcontainer/devcontainer.json```{
"name": "Alpine",
"image": "mcr.microsoft.com/devcontainers/base:alpine-3.20",
"containerUser": "vscode",
"remoteUser": "vscode",
"runArgs": [
"--userns=keep-id"
],
"containerEnv": {
"HOME": "/home/vscode"
}
}
The text was updated successfully, but these errors were encountered: