You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Create or edit a CasaOS app.
Create or edit a Volume mapping
Append :ro to target path
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
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.
The text was updated successfully, but these errors were encountered:
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
:ro
to target path/target/path:ro:rw
is not a valid mappingExpected 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
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.
The text was updated successfully, but these errors were encountered: