Read-only overlayfs support #596
Closed
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
|
There is already an implementation of overlayfs support in #547, which is further along. Please could you review that implementation and look into solving its remaining issues, rather than starting a new one? |
|
Ah, missed it. I'll look into it. |
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.
This is very much a WIP commit but I'd like to hear some thoughts if this is an idea worth perusing more.
The overlayfs would be used in flatpak for /etc. We have no way of updating a symlink from /etc/localtime into /etc/zoneinfo after the container has been created. With the overlayfs the symlink is just a file an overlayed tree and the kernel makes sure this all works out.
Flatpak POC is here flatpak/flatpak#5528