-
Notifications
You must be signed in to change notification settings - Fork 3
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
slirp4netns package missing in F40 base commit #547
Comments
Same bug here, this is still needed also for Podman: DNS is not working at all for rootless containers on F40. |
This comment was marked as off-topic.
This comment was marked as off-topic.
I think it would be a good idea to add slirp4netns back, I forgot to mentioned the case for older containers in the blog (I will update it). |
@Luap99 Can you convert to pasta? I'm new to Podman, so I assume podman network rm name, and recreate is enough, right? :) It's weird switching back fixed the issue, so hopefully it will all be solved soon. If you need more testing or debug info, let me know. Thanks! |
if you use named networks then it uses whatever is configured (default_rootless_network_cmd, pasta by default) although you will need to stop all containers to apply that on the next start for the rootless-netns. I was specifically talking about the default --network=slirp4netns (4.X) vs --network=pasta (5.0) |
We had a similar discussion in #246 when that happen for containernetworking-plugins. I'm not opposed to adding it back (although it's a bit late for the F40 release, but it can land in an update after) but then we need to plan for removing it in the future. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
I'll make a PR to add |
|
I merged both PRs so this should be fixed in the next update (likely tomorrow) |
Keep slirp4netns for rootless containers until it's fully deprecated in podman. See: fedora-silverblue/issue-tracker#547 See: https://blog.podman.io/2024/03/podman-5-0-breaking-changes-in-detail/
Keep slirp4netns for rootless containers until it's fully deprecated in podman. See: fedora-silverblue/issue-tracker#547 See: https://blog.podman.io/2024/03/podman-5-0-breaking-changes-in-detail/
Describe the bug
I'm trying to run a specific docker container with
docker start
, which outputs thisThe
slirp4netns
package is indeed not installed in the F40 current base commit, though it was in F39Returns nothing
Returns the package name.
Adding
slirp4netns
as a layered package allows to run the container properly.To Reproduce
Please describe the steps needed to reproduce the bug:
Expected behavior
The package being installed and
docker start
executingOS version:
The text was updated successfully, but these errors were encountered: