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
Volume mount readonly boolean value is not read correctly #18995
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.
remote
Problem is in podman-remote
Comments
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jun 27, 2023
There was a huge cut and paste of mount options which were not constent in parsing tmpfs, bind and volume mounts. Consolidated into a single function to guarantee all parse the same. Fixes: containers#18995 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jun 27, 2023
There was a huge cut and paste of mount options which were not constent in parsing tmpfs, bind and volume mounts. Consolidated into a single function to guarantee all parse the same. Fixes: containers#18995 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jun 27, 2023
There was a huge cut and paste of mount options which were not constent in parsing tmpfs, bind and volume mounts. Consolidated into a single function to guarantee all parse the same. Fixes: containers#18995 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jun 27, 2023
There was a huge cut and paste of mount options which were not constent in parsing tmpfs, bind and volume mounts. Consolidated into a single function to guarantee all parse the same. Fixes: containers#18995 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Jun 27, 2023
There was a huge cut and paste of mount options which were not constent in parsing tmpfs, bind and volume mounts. Consolidated into a single function to guarantee all parse the same. Fixes: containers#18995 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
cgiradkar
pushed a commit
to cgiradkar/podman
that referenced
this issue
Jul 12, 2023
There was a huge cut and paste of mount options which were not constent in parsing tmpfs, bind and volume mounts. Consolidated into a single function to guarantee all parse the same. Fixes: containers#18995 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
ashley-cui
pushed a commit
to ashley-cui/podman
that referenced
this issue
Jul 12, 2023
There was a huge cut and paste of mount options which were not constent in parsing tmpfs, bind and volume mounts. Consolidated into a single function to guarantee all parse the same. Fixes: containers#18995 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
cgiradkar
pushed a commit
to cgiradkar/podman
that referenced
this issue
Jul 13, 2023
There was a huge cut and paste of mount options which were not constent in parsing tmpfs, bind and volume mounts. Consolidated into a single function to guarantee all parse the same. Fixes: containers#18995 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
ashley-cui
pushed a commit
to ashley-cui/podman
that referenced
this issue
Jul 13, 2023
There was a huge cut and paste of mount options which were not constent in parsing tmpfs, bind and volume mounts. Consolidated into a single function to guarantee all parse the same. Fixes: containers#18995 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
cgiradkar
pushed a commit
to cgiradkar/podman
that referenced
this issue
Jul 17, 2023
There was a huge cut and paste of mount options which were not constent in parsing tmpfs, bind and volume mounts. Consolidated into a single function to guarantee all parse the same. Fixes: containers#18995 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
cgiradkar
pushed a commit
to cgiradkar/podman
that referenced
this issue
Jul 17, 2023
There was a huge cut and paste of mount options which were not constent in parsing tmpfs, bind and volume mounts. Consolidated into a single function to guarantee all parse the same. Fixes: containers#18995 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
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 26, 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.
remote
Problem is in podman-remote
Issue Description
Here's what the doc says about the volume mount
readonly
option:and the example
But if you run this:
and you will get
If you remove the
ro
orreadonly
option, it will become writable, like thisSo it turned out that the document was not correct, or the implementation of volume option parsing is wrong. Boolean value should be parsed instead of just checking
readonly
option appears or not.Steps to reproduce the issue
Run
or
Describe the results you received
Describe the results you expected
It should be writable if the readonly option is set to
false
.podman info output
The text was updated successfully, but these errors were encountered: