docs/filesystem: Weaken stateoverlay wording and direct to alternatives #1191
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
We wrote the code and it is useful. We are probably just going to need to support it into the forseeable future. However, my core problem with it is what I wrote in the docs here: it has no equivalent in the docker/podman ecosystem, which I think cuts against a core principle that we're trying to make the booted host align with containers. Of course, stateoverlay isn't a lot of code, and in theory it's a bit independent of ostree, so perhaps we could try to split it out at some point and then it could be used by e.g. `podman run --mount=type=stateoverlay` or so. Before anyone starts just blindly enabling stateoverlays I'd like them to have considered alternatives such as the symlink approach. Signed-off-by: Colin Walters <walters@verbum.org>
github-actions
bot
added
documentation
|
cc @jlebon in case you want to tweak things |
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.
We wrote the code and it is useful. We are probably just going to need to support it into the forseeable future. However, my core problem with it is what I wrote in the docs here: it has no equivalent in the docker/podman ecosystem, which I think cuts against a core principle that we're trying to make the booted host align with containers.
Of course, stateoverlay isn't a lot of code, and in theory it's a bit independent of ostree, so perhaps we could try to split it out at some point and then it could be used by e.g.
podman run --mount=type=stateoverlayor so.Before anyone starts just blindly enabling stateoverlays I'd like them to have considered alternatives such as the symlink approach.