(Rawhide/F28) Drop --noboot from container image creation
When building Fedora Server base images (such as when building F27 Modular Server), the --noboot option results in the container image attempting to mount /boot with XFS like the rest of the system. This results in the image-creation failing. Since the partitions don't matter in the end (the files are tarred up and shipped that way), we'll skip this optimization. Signed-off-by: Stephen Gallagher <sgallagh@redhat.com>
This commit is contained in:
parent
f1babff154
commit
41ef546b3f
@ -27,7 +27,7 @@ reboot
|
|||||||
# boot partitions are irrelevant as the final container image is a tarball
|
# boot partitions are irrelevant as the final container image is a tarball
|
||||||
zerombr
|
zerombr
|
||||||
clearpart --all
|
clearpart --all
|
||||||
autopart --noboot --nohome --noswap --nolvm
|
autopart --nohome --noswap --nolvm
|
||||||
|
|
||||||
%packages --excludedocs --instLangs=en --nocore
|
%packages --excludedocs --instLangs=en --nocore
|
||||||
fedora-modular-release
|
fedora-modular-release
|
||||||
|
Loading…
Reference in New Issue
Block a user