Hi,
[email protected] writes: > Hi Guix Community, > > I was able to boot an guix system instance an Incus (formerly LXD) container > using the following setup: > > lxc.environment = GUIX_NEW_SYSTEM=/gnu/store/(some hash here)-system > lxc.pinit.cmd = /gnu/store/(some hash here)-guile/3.0.9 /gnu/store/(some hash > here)-boot > For me to better understand, is this file accessible and editable from the container? Or is it a file on the host-side that is not controlled by the container system? > This works but I need to update this setup with updated hashes every time I > reboot the guix system container after guix pull / guix system reconfigure, > otherwise I will get stuck with the old guix system enviornment. > > Is there any file on a guix system telling us where is the latest system and > boot the booting process should source before populating /run/current-system > ? Obtain it, but from within where? That's quite important. Are you obtaining it from the host system or from the container (Guix System)? Then the solutions would differ. If it was possible to modify the LXC configuration file from within the container, the best solution would probably be writing up a custom bootloader for your operating-system that would set up / modify this file in question. It would get all the necessary information for obtaining path to the latest generation as well as all other ones. If that is out of the question, then the best I can think of is to look at the current system profile in `/var/guix/profiles/system` inside of the container's fs. You might even be able to go as far as putting `/var/guix/profiles/system` to the boot arguments. But I am not completely sure if symlinks are honored. Rutherther > > Thank you!
