-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Machine Start fail in user-mode networking #20982
Comments
Hello, the issue is in podman-wsl-fedora archive I created as a workaround, you can download an older rootfs.tar.xz file from https://github.com/containers/podman-wsl-fedora like for example last week https://github.com/containers/podman-wsl-fedora/releases/tag/v38.0.51 then, do |
Thank you for the quick reply! However, unfortunately I still get the same error even after downloading the suggested file from last week (https://github.com/containers/podman-wsl-fedora/releases/tag/v38.0.51) and running I do get the message that the machine init was completed (as usual), but after
This is for a Windows machine, so I'm running it from CMD in Windows. When installing Podman I did end up installing Ubuntu as well together with the WSL2 download requirements, but after reading the docs it looks like I should be able to run Podman commands from Windows CMD without problems. If my assumption is wrong, please let me know. I'm using WSL 2.0.14.0 and Podman version 4.8.2. Thank you! |
@lucasjl you need to do first: |
I ran into the same issue, and finding @lucasjl 's ticket from 7 hours previous, figured it couldn't be a coincidence and tried purging and rolling back to 4.7.2 and recreating the machine's and the problem didn't go away. I'm pretty sure it worked when we first tried it last week on 4.7.2 though, and I had unregistered and recreated all podman WSL instances when I tried rolling back. I did notice on the podman-net-usermod WSL instance, that in /var/log there was "vm.err" that would appear as soon as I tried to start up the main podman machine. It was because it did not have execute permission on the app/command 'vm'. So maybe my issues is related to rootless or some other permission config, as this is my first time using podman and am still not clear on that aspect. |
@grgghrn can you run |
I had to do a podman machine rm first, otherwise it kept saying the machine still exists when I try to init again, but beyond that, it does seem to be working (still rolled back to 4.7.2). I tried it rootless and --rootful and seems to work either way too. Not sure what I did differently when I tried rolling back at first, but must have missed something. I'm in no rush, I will stick with 4.7.2 and wait for the next release with your fix in it. Thank you! |
It worked now. Thank you so much for the quick and efficient help! As recommended by @benoitf I was able to make it work by getting an older version of rootfs.tar.xz on https://github.com/containers/podman-wsl-fedora/releases/tag/v38.0.51 and then applying these commands on CMD:
|
@lucasjl @grgghrn you don't have to wait for an updated podman release. A corrected image (v39.0.4) was pushed yesterday, which is pulled by all versions of podman during a new podman machine init. You just need to make sure that you remove any existing podman-net-usermode dist ( |
Issue Description
I have created a podman machine with -user-mode-networking via cli, and when I want to start it I have an error for -user-mode networking with exit status 42
PS : I'm in win10 and wsl is up to date
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
Describe the results you expected
.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: