-
Notifications
You must be signed in to change notification settings - Fork 6
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 #3
Comments
I think this would be good. From looking at the docs you should be able to pull the image from dockerhub or build it directly with podman. Is there any specific change you needed? |
Correct, I can use an image from Docker hub but have to modify the Dockerfile(e.g. |
So it looks like you need to use the long form to pull: podman pull etrombly/rust-crosscompile:latest it worked as root for me, I didn't set up to run as a regular user to test though. |
Long version worked for me as well, but we can't run it as a regular user, which is the point of Podman. Podman is made to be rootless docker, so that you can get rid of many root exploits which are on docker. |
I have a note about your reply.
because Podman tries to search their repos and can't find it. This is the problem I get with the Podman when run as non-root.
|
The permissions problem is because I run the compile and package as a different user in the container. For docker containers it makes sense, because you don't want to run things as root if you don't have to. But in rootless podman, root is actually the user you launch podman with. I see three options for fixing it:
Also if you are running on a system that has SELinux configure you may need to add :z to the end of the volume parameter.
Not sure which would be the best, 1 is probably the easiest. Have to think on it a bit. |
I changed it back to running as root to build, can you test to see if that fixes it for you? |
Surely, |
Because docker has some limitations, especially the "must-be-root-to-run" one, I'd love to see Podman support, as it's often impossible to run docker as a root.
The text was updated successfully, but these errors were encountered: