bump up IMG_SIZE to correct apt failure, correct sudo missing errors (?)#8
Open
geedubess wants to merge 14 commits into
Open
bump up IMG_SIZE to correct apt failure, correct sudo missing errors (?)#8geedubess wants to merge 14 commits into
geedubess wants to merge 14 commits into
Conversation
added 14 commits
January 15, 2026 11:11
Collaborator
|
Hey @geedubess thanks for the contribution and I'm sorry for only getting back to you now. Can you take a look at the |
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
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.
There were a bunch of commands seemingly not executing in stage2 because they were prefixed by sudo but it was not reportedly installed at that point in the build. When I removed 'sudo' from those commands, there was not enough free space in the rootfs image so I bumped up the free space calculation slightly.
I don't fully understand the sudo thing because I think the code WAS executing properly in previous builds, but someone who understands the build process might have insights!
(tested only as a docker build)