unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: System configuration on non-GuixSD systems (Debian)
Date: Fri, 25 Aug 2017 15:46:15 +0200	[thread overview]
Message-ID: <20170825134615.GA17316@thebird.nl> (raw)
In-Reply-To: <87efs0w059.fsf@elephly.net>

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.

      reply	other threads:[~2017-08-25 13:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22  9:23 System configuration on non-GuixSD systems (Debian) Pjotr Prins
2017-08-22  9:47 ` Christopher Baines
2017-08-25  7:56   ` Ricardo Wurmus
2017-08-25 13:46     ` Pjotr Prins [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170825134615.GA17316@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).