add ubuntu-keyring sources needed when rebuilding rootfs#1564
Open
meeg wants to merge 2 commits into
Open
Conversation
Signed-off-by: Sho Uemura <suemura@fnal.gov>
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.
When building a ZCU208 image with
REBUILD_PYNQ_ROOTFS=1, multistrap was giving me the same error (E: Can't find a source to download version '2021.03.26' of 'ubuntu-keyring:amd64') reported by https://discuss.pynq.io/t/pynq-image-v3-1-for-pynq-z1-build-fails-during-rootfs-multistrap-ubuntu-keyring-error/8691.It looks like this error is related to secure apt (https://manpages.ubuntu.com/manpages/jammy/man1/multistrap.1.html#secure-apt) and the fix is to either use
--no-author add the APT repository with the ubuntu-keyring sources before running multistrap. Here I tweak the Dockerfile and create_rootfs.sh to do the latter.I'm also moving the tzdata configuration into its own command, for ease of understanding - this isn't strictly necessary, it's just something that confused me during debugging.