Apparently, BusyBox's `cp` does NOT copy SELinux contexts when the `-a` argument is specified. This differs from GNU coreutils's `cp`, and explains why the files copied from the rootfs image to the persistent storage volume were not being labelled correctly. The `-c` argument is required. Now that files are labelled correctly when they are copied, the step to run `restorecon` is no longer necessary. |
||
---|---|---|
overlay | ||
patches/ebuilds/sys-boot/grub | ||
repos | ||
yellow | ||
.gitignore | ||
.gitmodules | ||
Makefile | ||
README.md | ||
build-grub.sh | ||
build-host-tools.sh | ||
build-kernel.sh | ||
build-rootfs.sh | ||
build-squashfs.sh | ||
build-update.sh | ||
build.sh | ||
config.txt | ||
genimage.cfg | ||
genimage.sh | ||
grub.cfg | ||
install-update.sh | ||
ocivm.sh | ||
podman-build.sh | ||
post-build.sh | ||
prepare.sh | ||
rebuild-pkg.sh | ||
setup-local-repo.sh | ||
start-container.sh | ||
vm-build.sh |
README.md
Errors
SWIOTLB Buffer
OF: reserved mem: failed to allocate memory for node … Can not allocate SWIOTLB buffer earlier and can't now provide you with the DMA bounce buffer
Ensure start_x=1
is in config.txt
and start_file
/fixup_file
are not
specified.
U-Boot: Overwrite Reserved Memory
** Reading file would overwrite reserved memory **
Set CONFIG_LMB_MAX_REGIONS=16
in u-boot/.config