mirror of
https://gitlab.com/alemaire/image-specs.git
synced 2025-01-11 02:03:30 +00:00
Fix the chroot step introduced in my previous commit
${ROOT?} does not make sense within a chroot, was causing the build to fail
This commit is contained in:
parent
554020cc94
commit
79a32b324d
@ -128,7 +128,7 @@ steps:
|
|||||||
# the partition labeled raspiroot instead of forcing it to mmcblk0p2
|
# the partition labeled raspiroot instead of forcing it to mmcblk0p2
|
||||||
- chroot: root-fs
|
- chroot: root-fs
|
||||||
shell: |
|
shell: |
|
||||||
sed -i 's/.dev.mmcblk0p2/LABEL=raspiroot/' ${ROOT?}/boot/firmware/cmdline.txt
|
sed -i 's/.dev.mmcblk0p2/LABEL=raspiroot/' /boot/firmware/cmdline.txt
|
||||||
|
|
||||||
# TODO(https://github.com/larswirzenius/vmdb2/issues/24): remove once vmdb
|
# TODO(https://github.com/larswirzenius/vmdb2/issues/24): remove once vmdb
|
||||||
# clears /etc/resolv.conf on its own.
|
# clears /etc/resolv.conf on its own.
|
||||||
|
Loading…
Reference in New Issue
Block a user