Christopher Baines <[email protected]> writes: > On Tue, 22 Aug 2017 11:23:25 +0200 > Pjotr Prins <[email protected]> wrote: > >> I need to reinstall a Debian server (again) and I am looking at how I >> can use 'guix system' to configure stuff. I remember there was someone >> who wrote a about configuring on non-GuixSD, but can't find the >> material (I need Debian because it has CUDA). >> >> Let's say I want sshd. It would make sense to me to create a package >> for openssh-with-config-for-machine, i.e., a modified sshd_config. The >> config file can sit in the store somewhere and I can symlink to a >> profile from /etc/sshd on this box so it gets picked up. […] > > One maybe bizare suggestion that comes to mind is to use a container > created through the `guix system container` command. > > This would allow you to create a set of processes, that you could give > access to specific parts of the host filesystem (using the --share and > --expose options), and expose the host network to if you want to > use services which access the network (only with this patch [1]).
This is an interesting idea. We can already run some services in containers, so maybe we can extend this some more and “build” the closure of a service and then spin it up with a non-PID-1 instance of shepherd. I think it would be very useful to have self-contained service blobs that are backed by a shared store. -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net
