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

Podman support #406

Open
hakong opened this issue Jun 13, 2022 · 8 comments
Open

Podman support #406

hakong opened this issue Jun 13, 2022 · 8 comments

Comments

@hakong
Copy link

hakong commented Jun 13, 2022

Does Motuz have support for Podman (the rootless version of docker, from Red Hat)?

@hakong
Copy link
Author

hakong commented Jun 13, 2022

Relates a bit to #405 as well. Podman uses the podman-compose command as a drop-in replacement for docker-compose or docker compose.

@dtenenba
Copy link
Contributor

I have not heard of Podman before today but I imagine the answer is no. The celery container in Motuz needs to run as root and then "become" other users by using the su command, so users have appropriate permissions on the filesystems mounted into the container.

@hakong
Copy link
Author

hakong commented Jun 13, 2022

Alright, cool. Podman is supposedly more secure by design so I guess podman support would be cool. It's also the default container software in the Red Hat os-family. But no big deal if this isn't on the roadmap.

@hakong
Copy link
Author

hakong commented Jun 13, 2022

I'll give it a stab later this week, maybe it works fine. If Motuz doesn't need anything run as root then it should work without much hassle.

@dtenenba
Copy link
Contributor

Motuz as it stands currently definitely needs to run as root - at least the celery container does. It may be possible to refactor it to use a setuid binary or other workarounds but I do not expect it to work out of the box with podman and without root.

@hakong
Copy link
Author

hakong commented Jun 13, 2022

What does the celery container do that requires root access?

@dtenenba
Copy link
Contributor

It runs as root because it kicks off copy jobs which run as logged in users. So if I log in as jdoe, the celery container will run a command as me by using the su command. This can only be done with root permission.

@hakong
Copy link
Author

hakong commented Jun 13, 2022

Ok, makes sense. That's less fun to run as non-root :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants