Unbreak 'create' on Silverblue #276
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
debarshiray
referenced
this pull request
Sep 26, 2019
Podman defaults to bind-mounting locations as read-write when neither 'rw' nor 'ro' is explicitly specified. On Silverblue /usr is mounted read-only on the host. Therefore, it's not possible to bind-mount it as read-write inside the toolbox container. It turns out that Podman doesn't downgrade the default mount flag to read-only when the source location is such, and this breaks creating new toolbox containers on Silverblue. See: containers/podman#4061 Fallout from d63b0a9 https://github.com/debarshiray/toolbox/pull/276
debarshiray
force-pushed
the
wip/rishi/silverblue-mount-usr-ro
branch
from
ae2c290
to
27707dc
Compare
Podman defaults to bind-mounting locations as read-write when neither 'rw' nor 'ro' is explicitly specified. On Silverblue /usr is mounted read-only on the host. Therefore, it's not possible to bind-mount it as read-write inside the toolbox container. It turns out that Podman doesn't downgrade the default mount flag to read-only when the source location is such, and this breaks creating new toolbox containers on Silverblue. See: containers/podman#4061 Fallout from d63b0a9 https://github.com/debarshiray/toolbox/pull/276
debarshiray
force-pushed
the
wip/rishi/silverblue-mount-usr-ro
branch
from
27707dc
to
32bd215
Compare
debarshiray
referenced
this pull request
Feb 15, 2021
This is meant to alleviate some of the pain of not being able to modify the list of bind mounts once a toolbox container has been created. For some cases, especially where read-only access is enough, one can get by with setting up symbolic links inside the toolbox container. Based on an idea from Colin Walters. https://github.com/debarshiray/toolbox/pull/264
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Podman defaults to bind-mounting locations as read-write when neither
'rw' nor 'ro' is explicitly specified.
On Silverblue /usr is mounted read-only on the host. Therefore, it's
not possible to bind-mount it as read-write inside the toolbox
container.
It turns out that Podman doesn't downgrade the default mount flag to
read-only when the source location is such, and this breaks creating
new toolbox containers on Silverblue. See:
containers/podman#4061
Fallout from d63b0a9