-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Uninformative slirp4netns
ERROR when portmapping
#2778
Comments
You probably have a too-early |
Wow, that was fast.
Indeed. Need to check how to get that running in |
Yeah, you need a 0.3.0 or later release to have port-forwarding support. The project lives at https://github.com/rootless-containers/slirp4netns and should be easy enough to build/install, though you might want to ping the package maintainers for Arch (assuming that you're using the official packages) and ask them to update. |
Ok. Just browsed by the |
That might actually not be accurate anymore - @giuseppe can you confirm that Slirp 0.3.0 is what we'd consider stable? (I suspect that we forgot to update the readme for the new slirp release) |
Oh - that would be wonderful. |
... but the tags imply pre-release state ... |
yes, slirp 0.3 is what we need and consider it stable |
Can you please initiate an appropriate |
There's a proper 0.3 release now that has already percolated into the ArchLinux repos and I can now start the container - in principle this could be closed. |
I am currently trying to write a tutorial on how to deploy certain network services easily using containers. The platform for the basis is Ubuntu 18.04 LTS. I wanted to try first Docker using the Snap packages but it is not mature enough, so it makes for over complicated setup and I miss the goal of "teaching how to deploy network services". So I went to Podman. Installation was a bliss and the However, when trying the next level of "hello world" it failed. I simply tried the following: $ podman run --detach --name nginx -p 8080:80 docker.io/nginx:stable
Trying to pull docker.io/nginx:stable...Getting image source signatures
Copying blob 8ca774778e85 done
Copying blob 0f23e58bd0b7 done
Copying blob 27833a3ba0a5 done
Copying config 295c7be079 done
Writing manifest to image destination
Storing signatures
Error: slirp4netns failed And as I understand the above thread, this is simply because I have the wrong version of slirp4netns. When I installed Could you upgrade the version available in the PPA for Ubuntu? PS: of course I could install the package from source, but again like for Snap, it is getting me away from my main goal and make the installation more complex. However, I was impress by the rest of podman, and this is a small fix (uploading the new release of a package) as I understand it. So I hope this could be fixed soon. PS2: perhaps a tutorial could be written about how networking works with Podman. A simple example like I was trying above to start with and then more advanced configurations. From the man page, I can see that there is also bridge and other networking. But nothing is currently explained how to use those options. I obviously tried to run using |
I cannot help with the |
@giuseppe PTAL |
I can write down some information on how the networking works with slirp4netns, what would be the best place for it? A blog post? @AkihiroSuda have you already written down something like that? |
slirp4netns has the man page, but probably better to have a doc/blog in Podman's own repo/website for clarifying how Podman works with slirp4netns. |
I'm a bit new to podman, but working through some basics, I'm running into:
Then I get the error trying to run
Complete error:
I'm not sure how to troubleshoot this. Maybe the container is not properly setup for ubuntu 18.04 and I should build my own with buildah? That's what I'll try next, but would love any tips if someone has some insight. |
Seems the port is either less than 1024 or already taken by another process |
Yes that was it, my system installed postgres was also on default port 5432, my bad, user error. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Running unprivileged (rootless) container on
ArchLinux
(usingdnsmasq
andshorewall
) gives uninformativeERRO[0006] slirp4netns failed
. Same operation asroot
works.Steps to reproduce the issue:
Install
podman
.Pull
alpine
:podman pull alpine
Run container while portmapping
docker
-equivalently:podman run -d --log-level=debug -p 127.0.0.1:8787:8787 docker.io/library/alpine
Describe the results you received:
See the attached (podman.log) output of
podman run -d --log-level=debug -p 127.0.0.1:8787:8787 docker.io/library/alpine 2> /tmp/podman.log
: container fails with non-descriptslirp4netns
error.Describe the results you expected:
Container starts with port forwarding to localhost.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Additional environment details (AWS, VirtualBox, physical, etc.):
ArchLinux
withdnsmasq
local dns caching andshorewall
running - eqivalentdocker
install uses dedicated bridge. How does podman handled this? Can't find info in debugging this networking(?) problem.The text was updated successfully, but these errors were encountered: