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

Can't Map Read-only Volumes #1788

Open
jaknz opened this issue Apr 18, 2024 · 0 comments
Open

Can't Map Read-only Volumes #1788

jaknz opened this issue Apr 18, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@jaknz
Copy link

jaknz commented Apr 18, 2024

Describe the bug
Following Docker standards, I should be able to mount a volume as read-only by appending the :ro tag. However it appears CasaOS is silently appending an invisible :rw tag which breaks this functionality.

To Reproduce

  1. Create or edit a CasaOS app.
  2. Create or edit a Volume mapping
  3. Append :ro to target path
  4. CasaOS throws up an error indicating that /target/path:ro:rw is not a valid mapping

Expected behavior
The :rw tag is not required to mount a volume, as it is the default behaviour. Expected behaviour would then be for me to be able to specify (or not) this tag.

If you desperately want to include an explicit read-write or read-only tag, would you consider adding a tick box for each volume that indicates write status as read-write (ticked) or read-only (unticked) instead?

Screenshots
CasaOS ro-rw

Desktop (please complete the following information):
Not relevant to bug report

System Time
Not relevant to bug report

Logs
Not relevant to bug report

Additional context
Running CasaOS v0.4.8, reported as up-to-date.

@jaknz jaknz added the bug Something isn't working label Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant