[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: System configuration on non-GuixSD systems (Debian)
From: |
Pjotr Prins |
Subject: |
Re: System configuration on non-GuixSD systems (Debian) |
Date: |
Fri, 25 Aug 2017 15:46:15 +0200 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Fri, Aug 25, 2017 at 09:56:50AM +0200, Ricardo Wurmus wrote:
> > 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.
Yes. Not for sshd, but for many other things yes :)
> I think it would be very useful to have self-contained service blobs
> that are backed by a shared store.
I am planning to host a number of services on Pi3, including mail and
http(s). It looks like we are pretty close to achieving this with
containers. Do containers actually run on Arm? Docker has it
http://blog.hypriot.com/getting-started-with-docker-on-your-arm-device/
so it should be possible.
Pj.