Increase Radxa E20C rootfs for Docker builds#2
Closed
tacomilkshake wants to merge 1 commit into
Closed
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
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.
Summary
rootfs_size_mb: 2048for the Radxa E20C recipeMAX_CUSTOM_ROOTFS_SIZE_MBto 4096 so the recipe validatesrootfs_size_mbfieldRepro
Before this change, the build fails during ImageBuilder
root.ext4creation with:The failed ASU request had
rootfs_size_mb: null, so ImageBuilder used the default small rootfs even though the target E20C devices have 16 GB eMMC.Validation
Validated on Ranch with Radxa E20C + eMMC install + Tailscale + Docker selected. The rebuilt request included
rootfs_size_mb: 2048and completed successfully.Depends on firmware-selector PR: orbforge/firmware-selector-openwrt-org#2