From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
To: help-guix <help-guix@gnu.org>
Subject: A few questions about guix containers
Date: Sat, 11 May 2019 16:21:40 +0200 [thread overview]
Message-ID: <87sgtlxea3.fsf@gmail.com> (raw)
Hello,
I'm trying to get to grips with Guix's container support.
Specifically, I can create containerised system using
$ guix system container /path/to/sysconf.scm
I should then be able to run commands in that container using
$ guix container exec PID CMD
But here's the rub: how do I find the PID of the container launched
using 'guix system container'?
Also, I can relatively straight forwardly map network ports to guix
systems using
$ guix system vm /path/to/sysconf.scm
and qemu's -net user,hostfwd syntax
Can I achieve similar mappings using 'guix system container'?
Is anyone using containers to test complex networked services in system
configurations?
Best wishes,
Alex
next reply other threads:[~2019-05-11 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-11 14:21 Alex Sassmannshausen [this message]
2019-05-11 22:25 ` A few questions about guix containers Christopher Baines
2019-05-27 12:52 ` Alex Sassmannshausen
2019-05-28 18:38 ` Christopher Baines
2019-05-28 5:53 ` Arun Isaac
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=87sgtlxea3.fsf@gmail.com \
--to=alex.sassmannshausen@gmail.com \
--cc=help-guix@gnu.org \
/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).