You are not logged in.
First, a little background.
I am using the bootstrap files system, arch-chrooting into it, installing base, and running mkinitcpio.
This works when I run it locally on my Arch system, as expected.
For reasons that would take a little more time to explain, I also need to execute this procedure within a docker container. When running with --privileged in docker, arch-chroot and stuff should be have similar as if I was running it locally. For the most part, this is true, except for mkinitcpio.
Here is two output files. One running on host, one running through docker. Also included is a diff to help highlight the differences.
https://gist.github.com/pauldotknopf/d4 … d16b9466ec
My mkinitcpio.conf and preset is default, no changes.
Why do I get this fsck.overlay error? Also, why isn't ext4 support being added to the initcpio? I imagine because the cpio didn't finish building.
Last edited by theonlylawislove (2017-09-27 16:41:50)
Offline
Turns out that "autodetect" was causing the problems.
https://git.archlinux.org/mkinitcpio.gi … autodetect
Particularly, this line.
# detect filesystem for root
if rootfstype=$(findmnt -uno fstype -T '/'); then
add_if_avail "$rootfstype"
else
error "failed to detect root filesystem"
fs_autodetect_failed=1
fi
Since docker uses the overlay system, the autodetect script was trying to add it as a module.
Removing the autodetect fixed it. Now, mkinitcpio is deterministic, regardless of the platform it is run on.
Offline
Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.
Offline