-
Notifications
You must be signed in to change notification settings - Fork 355
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
Set network namespace in the container #2473
Comments
Thanks for creating the issue. Why did they think that? I think youki apply the rest of the namespace here: |
You are 100% correct. |
Pods share a network namespace among the containers, right? If it is right, perhaps runwasi is responsible for creating a network namespace for a pod. But I'm not sure... |
This is how containerd-shim works. The network namespace is created upfront and the With that being said, I think it is possible to use |
Close this issue since |
From all the namespaces specified in the container spec,
youki
only sets theuser
andpid
namespaces.Other namespace, like the
nerwork
namespace, are ignored.See containerd/runwasi#364 and this slack thread for context.
The text was updated successfully, but these errors were encountered: