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

How to mount new volume(s) into my home folder with podman run(rootless)? #4891

Closed
jonasbartho opened this issue Jan 17, 2020 · 3 comments
Closed
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@jonasbartho
Copy link

/kind bug ?

I really really want my firm to go away from docker and completely switch to rootless podman.... The only problem I have with rootless podman is that I can't mount new volumes in my own home folder? I asked Daniel Walsh 2 months-ish ago and he said that it should have been fixed in the master branch(I was using v1.6.2 on fedora 30 back then)

Now I am trying the same thing with podman v1.7.0 on Fedora 31 , but still without any success? Am I still doing something wrong?

Example that works with docker:
$ sudo docker run -v $HOME/neo4j/data:/data neo4j

What I try as rootless podman:
§ podman run --privileged -v $HOME/neo4j/data:/data neo4j
##error message:
Error: error checking path "/home/jonas/neo4j/data": stat /home/jonas/neo4j/data: no such file or directory

If i create the folders manually with my local user it works... but my users at my firm want to use the "--volume/-v" parameter to mount up new folders in their home folders...

PS: SELinux is temporarily disabled for troubleshoot purposes...

@openshift-ci-robot
Copy link
Collaborator

@jonasbartho: The label(s) kind/? cannot be applied, because the repository doesn't have them

In response to this:

/kind bug ?

I really really want my firm to go away from docker and completely switch to rootless podman.... The only problem I have with rootless podman is that I can't mount new volumes in my own home folder? I asked Daniel Walsh 2 months-ish ago and he said that it should have been fixed in the master branch(I was using v1.6.2 on fedora 30 back then)

Now I am trying the same thing with podman v1.7.0 on Fedora 31 , but still without any success? Am I still doing something wrong?

Example that works with docker:
$ sudo docker run -v $HOME/neo4j/data:/data neo4j

What I try as rootless podman:
§ podman run --privileged -v $HOME/neo4j/data:/data neo4j
##error message:
Error: error checking path "/home/jonas/neo4j/data": stat /home/jonas/neo4j/data: no such file or directory

If i create the folders manually with my local user it works... but my users at my firm want to use the "--volume/-v" parameter to mount up new folders in their home folders...

PS: SELinux is temporarily disabled for troubleshoot purposes...

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.

@openshift-ci-robot openshift-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jan 17, 2020
@rhatdan
Copy link
Member

rhatdan commented Jan 17, 2020

@jonasbartho You want it to create a new directory on your host when you mount it, and we decided to reject this fix. My problem with it, is it can lead to errors where a typo accidentally succeeds. If Docker creates new directories on the host, when you volume mount them in, I believe this is a bug.

To me this is like saying
mount -o bind /home/jonas/neo4j/data /mnt
and expecting the mount program to create /home/jonas/neo4j/data directory

@jonasbartho
Copy link
Author

Aha, thank you for this clarification @rhatdan! I see your point! 👍
Such small differences in comparison to docker like this one should be proper documented to avoid misunderstandings.

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 23, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

3 participants