-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
local registry script with rootless podman Error: "slirp4netns" is not supported: invalid network mode #2694
Comments
It seems that script does not work with podman rootless |
podman + rootless is doubly experimental. This script is only tested on docker but it does not do anything complex on the docker side, it should work. This feels like a podman bug. |
Not a "bug", simply |
/close |
@aojea: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
You can create a local registry by setting |
But how can we make good use of rootless podman with rootless podman network support? This combination is easy to come up in user thought but "unimplemented"? Or any workaround to let a podman container join "slirp4netns" network? |
FYI: rootless docker has |
Are there plans to implement this in |
This isn't really the best place to ask that. |
Seems like slirp4netns is default for podman here: https://docs.podman.io/en/stable/markdown/podman-network.1.html#slirp4netns Rootless containers references it also: https://rootlesscontaine.rs/getting-started/podman/#changing-the-port-forwarder |
This script works with podman, docker, rootless docker AFAIK. If anyone wants to look into contributing a fix for rootless podman and podman itself cannot be fixed: |
What happened:
slirp4netns networking error
What you expected to happen:
no error
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Using rootless podman
Environment:
kind version
): kind v0.12.0 go1.18 linux/amd64kubectl version
):docker info
):/etc/os-release
):The text was updated successfully, but these errors were encountered: