Skip to content
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

enable running rootless podman inside a pod #21514

Closed
TomasTomecek opened this issue Nov 19, 2018 · 4 comments
Closed

enable running rootless podman inside a pod #21514

TomasTomecek opened this issue Nov 19, 2018 · 4 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@TomasTomecek
Copy link
Contributor

We would like to run rootless podman containers inside openshift pods so that we can take advantage of openshift's scheduling superpowers and have access to a root environment (via user namespacing) from a pod.

We are tracking podman work for this in here: containers/podman#1092

In the current iteration, the blocker is that openshift is dropping cap_set_{uid,gid} capabilities which podman needs to construct a user namespace.

What would be the best way to solve this issue? Can a solution for this land in the default SCC?

Version
oc v3.11.0+0cbc58b
kubernetes v1.10.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO
Steps To Reproduce

https://github.com/TomasTomecek/rootless-podman-in-openshift

@cgwalters
Copy link
Member

See also containers/bubblewrap#284

For Kubernetes/OpenShift this also blocks on user namespaces kubernetes/enhancements#127

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 16, 2019
@jamescassell
Copy link

Fixed, or no longer desired?

@TomasTomecek
Copy link
Contributor Author

I'm no longer interested in this so I closed. Feel free to open a new one. (I think that it could possibly work with --isolation chroot)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

5 participants