test: test/demo flatpak installs via bootc-installer container #1134
Conversation
This file contains hidden or 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
Tiny commit that demos a container installer with integrated flatpaks. Its a bit messy but that is mostly because the bootc-installer is a bit messy (until we either have a base container or a script). It shows we can have installed flatpaks without any new concepts. Once flatpak/flatpak#6116 is available this can become even nicer, currently the install is done via a kickstart with explicit naming of the flatpaks, when we can use preinstall.d this becomes fully declarative. Search for "LOOK HERE:" in the test_build_iso.py for the relevant parts.
|
I also try to do a flatpak install in my kickstart file but I get :
Did you have similar issue ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Tiny commit that demos a container installer with integrated flatpaks. Its a bit messy but that is mostly because the bootc-installer is a bit messy (until we either have a base container or a script).
It shows we can have installed flatpaks without any new concepts. Once flatpak/flatpak#6116 is available this can become even nicer, currently the install is done via a kickstart with explicit naming of the flatpaks, when we can use preinstall.d this becomes fully declarative.
Search for "LOOK HERE:" in the test_build_iso.py for the relevant parts.