-
Notifications
You must be signed in to change notification settings - Fork 322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scripts now run on the host by default #1729
Comments
"putting the following snippet at the top of the script:" Please, don't leave us hanging... is this a null snippet or is it really missing? |
(Updated)
Is this going to break builds of projects like Build log:
|
Yes, check the HACKING guide in systemd, it explicitly documents that systemd depends on the latest mkosi from git. |
- Rename mkosi.default to mkosi.conf - Add mkosi.repart to define root partition - Add gzip to make sure generating locales - Add snippet to mkosi.build / mkosi.postinst - See: systemd/mkosi#1729
Hi @DaanDeMeyer , Sorry for my ignorance, I am new to mkosi. Why not make special scripts name, like "mkosi.prepare.chroot", "mkosi.build.chroot", and so on, that if its exist it will run inside chroot? Adding ( What is possible values for "$container" beside "mkosi" that make it need its only IF-condition? Just curious. |
@shuLhan See https://systemd.io/CONTAINER_INTERFACE/ which recommends container managers to set I also opened #1969 to implement your suggestion of running scripts with the ".chroot" extension in the image automatically. |
Build scripts are now executed on the host. See the
SCRIPTS
sectionin the manual for more information. Existing build scripts will need
to be updated to make sure they keep working. Specifically, most paths
in scripts will need to be prefixed with $BUILDROOT to have them
operate on the image instead of on the host system. To ensure the host
system cannot be modified when running a script, most host directories
are mounted read-only when running a script to ensure a script cannot
modify the host in any way. Alternatively to making the script run on
the host, the script can also still be executed in the image itself by
putting the following snippet at the top of the script:
The text was updated successfully, but these errors were encountered: