From: Giovanni Biscuolo <g@xelera.eu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, Joshua Marshall <j.marshall@arroyo.io>
Subject: Re: Declarative containers
Date: Tue, 26 Mar 2019 22:49:57 +0100 [thread overview]
Message-ID: <87zhphwbju.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <87zhphft98.fsf_-_@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
Hello,
thanks for your feedback Ludo'! :-)
Ludovic Courtès <ludo@gnu.org> writes:
[...]
> Given that we already have ‘guix system container’, declarative
> containers are a low hanging fruit.
"low hanging fruit" is much more expressive than "last mile" :-)
> We could have a ‘container’ (or ‘sub-system’?) service;
mumble: `container` is so abused that it's starting to become a buzzword
to my ears, `sub-system` is probably more semantic
> you’d pass it an <operating-system> and it’d create a Shepherd service
> that runs that OS in a container.
what is the method used to instantiate containers with Guix?
I know lxc/lxd and systemd-nspawn but can't still understand what's used
here
> That would be fun!
yep, a *lot* of fun
also, given Guile homoiconicity a web based (who wants web based
interfaces?!? bah?) and/or declarative orchestration system built on top
of Guix+GWL would be the next (not so low) hanging fruit :-D
uh, if only I was able to hack in guile... I'll get there but I'm so
sorry I cannot help _now_ :-S
Gio'.
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-03-26 21:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 17:47 Feature requests Joshua Marshall
2019-03-22 22:30 ` Julien Lepiller
2019-03-23 14:01 ` Joshua Marshall
2019-03-23 14:36 ` Julien Lepiller
2019-03-25 9:40 ` Giovanni Biscuolo
2019-03-25 17:38 ` Joshua Marshall
2019-03-26 17:19 ` Declarative containers Ludovic Courtès
2019-03-26 21:49 ` Giovanni Biscuolo [this message]
2019-03-27 11:18 ` Ludovic Courtès
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=87zhphwbju.fsf@roquette.mug.biscuolo.net \
--to=g@xelera.eu \
--cc=guix-devel@gnu.org \
--cc=j.marshall@arroyo.io \
--cc=ludo@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 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).