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

What's the podman equivalent of Docker's volume-opt parameter in mount strings? #13387

Closed
rhatdan opened this issue Mar 1, 2022 Discussed in #13378 · 4 comments · Fixed by #13788
Closed

What's the podman equivalent of Docker's volume-opt parameter in mount strings? #13387

rhatdan opened this issue Mar 1, 2022 Discussed in #13378 · 4 comments · Fixed by #13788
Assignees
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@rhatdan
Copy link
Member

rhatdan commented Mar 1, 2022

Discussed in #13378

Originally posted by dstaley February 28, 2022
I'm trying to translate the following --mount string from Docker to podman:

"src=services,dst=/services,volume-opt=device=:/volume3/Services,\"volume-opt=o=addr=ganymede.localdomain,vers=3,soft\",type=volume,volume-driver=local,volume-opt=type=nfs"

When running a container with this mount string, I get the error:

Error: volume-opt: invalid mount option

I understand that the options passed to --mount are basically parsed out and passed to the OS's underlying mount command, so I assume that volume-opt isn't getting translated to whatever it needs to be for mount to understand it.

I've seen a few sample commands that create volumes using --opt, however I don't see anything like that in the docs for the --mount argument.

@rhatdan
Copy link
Member Author

rhatdan commented Mar 1, 2022

@flouthoc PTAL

@github-actions
Copy link

github-actions bot commented Apr 3, 2022

A friendly reminder that this issue had no activity for 30 days.

@rhatdan
Copy link
Member Author

rhatdan commented Apr 5, 2022

@flouthoc have you had a chance to look at this?

@flouthoc
Copy link
Collaborator

flouthoc commented Apr 6, 2022

@rhatdan Above PR should close this. I am wondering why is this not documented by docker.

@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 20, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants