Extension versioning + runtime enable #60
Merged
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
Also update runtime construction to enable extensions for avocadoctl.
danielspofford
previously approved these changes
Nov 19, 2025
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 PR introduces breaking changes.
Previously, we would add extensions to the runtime via adding the images to /var/lib/avocado/extensions. Extension image names would only contain the extension names. This is problematic with staging an update to move from one version set of extensions to another.
This PR
version = "<SEMVER>".appbecomesapp-1.0.0.avocado buildvar part image creation to enable extensions by creating a directory at/var/lib/avocado/runtime/<rootfs os-release VERSION_ID>and adding symlinks to images in the/var/lib/avocado/extensions.Depends on avocado-linux/avocado-control#5