Why Podman tryes to create a new user namespace and storage in vscode terminal on ubuntu. #27812
Unanswered
romikforest
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi.
I had vscode installed in snap on ubuntu. And podman in vscode terminal every time created a new separate storage for containers (that not persisted after reboot) and could not work with systemd. So I uninstalled snap vscode and installed it from the microsoft repo. There are no custom settings or extensions. I've deleted all vscode data folders. There are no project files/folders opens. I just run vscode and see a welcome screen, open terminal window and run some trivial podman commands like podman ps or podman info. All these commands terminates without error messages with status 1. So I run command
podman --log-level=debug info. What I see: podman writesNot configuring container storeandCreating a new rootless user namespaceand exits. While podman in normal ubuntu terminal or pycharm terminal writesoverlay: starage already configured with a mount-programand doesn't try to create a new user namespace. It looks like same zsh is being run in all terminals and I even made exactly same environment variables in all kinds of terminal. They have the DOCKER_HOST environment variable and don't have XDG_DATA_HOME. I can't understand what triggers different podman behavior in vscode. The same user is active in all terminals.podman 5.7.1 (installed with homebrew). vscode 1.107.1. Ubuntu 24.03.3 LTS.
Is there a way to force podman in vscode just work as in other terminals, use my user's storage, my systemd etc?
Couldn't google any solution.
Thanks in advance.
Beta Was this translation helpful? Give feedback.
All reactions