From: conjaroy <conjaroy@gmail.com>
To: help-guix@gnu.org
Subject: Is anyone using `guix system container` in production?
Date: Wed, 29 Jul 2020 18:17:44 -0400 [thread overview]
Message-ID: <CABWzUjUBTKLzxn5xVrd6=_hgE91bdzTwoaPCxmhnS91TJH3H3g@mail.gmail.com> (raw)
I'm interested in deploying several system containers to a single cloud
VPS, and I had originally planned to build those via `guix system
docker-image`. Although Docker has some nice CLI tools for
starting/stopping/listing active containers, it occurs to me that an
alternative (`guix system container`) has at least one significant
advantage: containers come online in seconds, as opposed to the minutes it
takes to build and import a Docker image (or tens of minutes, if the build
host is a VM without /dev/kvm.) It might also be the case that using
/gnu/store for all containers is more disk-space-efficient than creating
self-contained Docker images for each one.
So I was wondering if anyone has experience running long-lived containers
built via `guix system container` in a production setting. Since I'm
running Guix on a foreign distro (Debian 10), it seems reasonable to build
a systemd service around the container script, but there may be pitfalls I
haven't considered:
# build container script and register it as a gc root with a well-known
name.
guix build --root=/home/guix/my-awesome-container $(guix system container
-d my-awesome-container.scm)
cat << EOF > /etc/systemd/system/my-awesome-container.service
[Unit]
Description=My Awesome Container
[Service]
ExecStart=/home/guix/my-awesome-container
TimeoutStopSec=30
StandardOutput=syslog
StandardError=syslog
[Install]
WantedBy=multi-user.target
EOF
next reply other threads:[~2020-07-29 22:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 22:17 conjaroy [this message]
2020-08-02 8:34 ` Is anyone using `guix system container` in production? Efraim Flashner
2020-08-02 15:40 ` conjaroy
2020-08-03 6:53 ` Efraim Flashner
2020-08-04 12:40 ` conjaroy
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABWzUjUBTKLzxn5xVrd6=_hgE91bdzTwoaPCxmhnS91TJH3H3g@mail.gmail.com' \
--to=conjaroy@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.