If calling the chroot command (e.g. systemd-nspawn, on a systemd system) fails, the rest of the image builder continues trying to execute, even though the chroot settings are broken.
This results in Jenkins claiming that the build succeeded even when it errored out at the beginning.