Re: How to use guix-publish with a restricted guix-daemon?
I worked around this by also setting the guix-publish user as the owner instead of root. This feels like a bit of a hack but it works. On 25.02.25 20:34, Dariqq wrote: Hello, I recently discovered that guix-configuration offers a way to set the permission and owner of the directory containing the daemon socket. My plan was to create a new group "guix" and only allow users of this group to use the daemon. And then also added my normal user to the guix group. The setup works great for a regular user but I had some issues with the guix-publish service as the guix-publish user also needs access to the daemon.
Re: Guix SD idiomatic system backup and restore
Those are all good points, thanks Edouard. I had considered using a guix system image definition to build an image that could be DD'd onto a new system disk. However, I'm using btrfs inside a cryptroot, and btrfs doesn't appear to be supported by the image definitions at present. On Tue, 18 Mar 2025, 11:21 Edouard Klein, wrote: > Hi ! > > That sounds about right. Be careful though that the guix installation > image often is widely out of date. It may therefore take quite long to > install your system, if it works at all (if will fail if you use > packages that were not defined when the installer was created, or if you > use channels). > > You'd need to guix pull at some point to get a guix that can understand > your configuration. > > Be careful also to how your current configuration references your > current boot disk, if you change disks, you may need to change that part > of the configuration as well. My advice would be to give a label to your > current disk, and apply the same label to the new disk, and then use > that in your operating-system declaration. > > Those are minor issues that you can forget unless you absolutely need to > be up and running less than one or two hours after a full disk failure. > Otherwise you can deal with them when the day comes. > > If however you can not handle any long downtime, then I strongly suggest > you address those two points and run a exercise just to make sure it > works and that your backups are actually operational. > > Cheers, > > Edouard. > > Laurence Rochfort writes: > > > Hello all, > > > > I have my whole system declaratively configured using config.scm and > > home-configuration.scm stored in my home directory. My entire home > > folder is backed up by btrbk every hour to an external location. > > > > Am I correct in thinking that to restore from a failed disk it is > sufficient to: > > > > - Boot guix installer > > - Partition disk > > - Provide existing config.scm to installer "guix system init" > > - Reboot into new system > > - Restore home folder from backup > > - Run "guix home reconfigure" > > > > > > Regards, > > Laurence >
Re: Guix SD idiomatic system backup and restore
Hi ! That sounds about right. Be careful though that the guix installation image often is widely out of date. It may therefore take quite long to install your system, if it works at all (if will fail if you use packages that were not defined when the installer was created, or if you use channels). You'd need to guix pull at some point to get a guix that can understand your configuration. Be careful also to how your current configuration references your current boot disk, if you change disks, you may need to change that part of the configuration as well. My advice would be to give a label to your current disk, and apply the same label to the new disk, and then use that in your operating-system declaration. Those are minor issues that you can forget unless you absolutely need to be up and running less than one or two hours after a full disk failure. Otherwise you can deal with them when the day comes. If however you can not handle any long downtime, then I strongly suggest you address those two points and run a exercise just to make sure it works and that your backups are actually operational. Cheers, Edouard. Laurence Rochfort writes: > Hello all, > > I have my whole system declaratively configured using config.scm and > home-configuration.scm stored in my home directory. My entire home > folder is backed up by btrbk every hour to an external location. > > Am I correct in thinking that to restore from a failed disk it is sufficient > to: > > - Boot guix installer > - Partition disk > - Provide existing config.scm to installer "guix system init" > - Reboot into new system > - Restore home folder from backup > - Run "guix home reconfigure" > > > Regards, > Laurence
Re: Guix SD idiomatic system backup and restore
I think you can work around that by creating a btrfs filesystem on an image file, mounting it, and guix system init-ing your system on the mount point, then unmounting. This is untested, and I'm not sure how to make it so the image doesn't take too much space. Maybe converting it to a qcow2 at some point ? These can be made sparse. Let me know if you succeed, I'm also interested in that. Laurence Rochfort writes: > Those are all good points, thanks Edouard. > > I had considered using a guix system image definition to build an image that > could be DD'd onto a new system disk. > > However, I'm using btrfs inside a cryptroot, and btrfs doesn't appear to be > supported by the image definitions at present. > > On Tue, 18 Mar 2025, 11:21 Edouard Klein, wrote: > > Hi ! > > That sounds about right. Be careful though that the guix installation > image often is widely out of date. It may therefore take quite long to > install your system, if it works at all (if will fail if you use > packages that were not defined when the installer was created, or if you > use channels). > > You'd need to guix pull at some point to get a guix that can understand > your configuration. > > Be careful also to how your current configuration references your > current boot disk, if you change disks, you may need to change that part > of the configuration as well. My advice would be to give a label to your > current disk, and apply the same label to the new disk, and then use > that in your operating-system declaration. > > Those are minor issues that you can forget unless you absolutely need to > be up and running less than one or two hours after a full disk failure. > Otherwise you can deal with them when the day comes. > > If however you can not handle any long downtime, then I strongly suggest > you address those two points and run a exercise just to make sure it > works and that your backups are actually operational. > > Cheers, > > Edouard. > > Laurence Rochfort writes: > > > Hello all, > > > > I have my whole system declaratively configured using config.scm and > > home-configuration.scm stored in my home directory. My entire home > > folder is backed up by btrbk every hour to an external location. > > > > Am I correct in thinking that to restore from a failed disk it is > sufficient to: > > > > - Boot guix installer > > - Partition disk > > - Provide existing config.scm to installer "guix system init" > > - Reboot into new system > > - Restore home folder from backup > > - Run "guix home reconfigure" > > > > > > Regards, > > Laurence
Guix SD idiomatic system backup and restore
Hello all, I have my whole system declaratively configured using config.scm and home-configuration.scm stored in my home directory. My entire home folder is backed up by btrbk every hour to an external location. Am I correct in thinking that to restore from a failed disk it is sufficient to: - Boot guix installer - Partition disk - Provide existing config.scm to installer "guix system init" - Reboot into new system - Restore home folder from backup - Run "guix home reconfigure" Regards, Laurence
