From: Arun Isaac <arunisaac@systemreboot.net>
To: Christopher Baines <mail@cbaines.net>, alex.sassmannshausen@gmail.com
Cc: help-guix <help-guix@gnu.org>
Subject: Re: A few questions about guix containers
Date: Tue, 28 May 2019 11:23:07 +0530 [thread overview]
Message-ID: <cu7muj7cegs.fsf@systemreboot.net> (raw)
In-Reply-To: <87y33cmxwz.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
> So I've been using guix system container with some success for a while
> now, but I've been relying on this old patch I wrote to add shared
> network support, in the same way that guix environment can do it [1]
>
> 1: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28128
>
> I haven't given it enough attention, but recently Arun Isaac looks to
> have picked it up, so I'm hopeful that this functionality might be more
> widely available soon.
I finished and pushed this patch to master a week ago. So, it is ready
for wider use! :-)
After this patch, I have started using this on my home server. The
server runs Parabola. I can't migrate all services immediately to
Guix. So, I have a Guix container running inside Parabola that runs some
of the services and the host Parabola runs the rest. Once I migrate all
services to the Guix container, I will simply replace Parabola with a
full Guix installation.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-05-28 5:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-11 14:21 A few questions about guix containers Alex Sassmannshausen
2019-05-11 22:25 ` Christopher Baines
2019-05-27 12:52 ` Alex Sassmannshausen
2019-05-28 18:38 ` Christopher Baines
2019-05-28 5:53 ` Arun Isaac [this message]
2019-05-28 10:14 ` Alex Sassmannshausen
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=cu7muj7cegs.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=alex.sassmannshausen@gmail.com \
--cc=help-guix@gnu.org \
--cc=mail@cbaines.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.
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).