From: Giovanni Biscuolo <g@xelera.eu>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Thompson, David" <dthompson2@worcester.edu>,
"Ricardo Wurmus" <rekado@elephly.net>,
"Olivier Dion" <olivier.dion@polymtl.ca>
Cc: help-guix <help-guix@gnu.org>, guix-devel@gnu.org
Subject: declarative containers (was Re: [EXT] Re: Enterprise Guix Hosting?)
Date: Mon, 23 Jan 2023 16:34:53 +0100 [thread overview]
Message-ID: <87wn5dgt7m.fsf@xelera.eu> (raw)
In-Reply-To: <878rmx3939.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1736 bytes --]
Hello everybody,
(this is an old thread started on help-guix [1])
Ludovic Courtès <ludo@gnu.org> writes:
> "Thompson, David" <dthompson2@worcester.edu> skribis:
>
>> On Wed, Aug 31, 2022 at 2:40 AM Ricardo Wurmus <rekado@elephly.net> wrote:
>>>
>>> Another thing that seems to be missing is a way to supervise and manage
>>> running containers. I use a shepherd instance for this with
>>> container-specific actions like this:
[...]
>> Hey that's a real nice starting point for a container management tool!
>> So maybe there should be a system service to manage containers and
>> then a 'docker compose'-like tool for declaratively specifying
>> containers and their network bridging configuration that is a client
>> of the service?
>
> Agreed! We could turn Ricardo’s code into ‘container-guest-service’ or
> something and have ‘containerized-operating-system’ add it
> automatically.
please there was some progress with this service?
once done, could it be possible to declaratively start a whole network
of containers using a dedicated home-service, or
containerized-operating-systems (also on foreign distros)?
right now with "guix system container" we can imperatively manage
(start/stop, connect to the console with nsenter) and connect them
to the network [2], Ricardo showed us how he do it programmatically;
having a declarative interface (os-records) whould be awesome!
I'm very interested and willing to test it, if needed
thanks! Gio'
[1] id:878rn4syql.fsf@elephly.net
[2] thank you Ricardo for the cookbook section!
https://guix.gnu.org/en/cookbook/en/guix-cookbook.html#Guix-System-Containers
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
next prev parent reply other threads:[~2023-01-23 15:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 23:23 Enterprise Guix Hosting? Yasuaki Kudo
2022-07-30 14:36 ` Olivier Dion via
2022-07-30 16:20 ` Phil
2022-07-30 23:18 ` Yasuaki Kudo
2022-07-31 0:42 ` Benjamin Slade
2022-07-31 11:01 ` Phil
2022-08-09 20:37 ` Ludovic Courtès
2022-08-09 22:24 ` Yasuaki Kudo
2022-08-14 9:53 ` Phil
2022-08-14 22:03 ` Yasuaki Kudo
2022-08-15 20:50 ` Phil
2022-08-25 18:37 ` Olivier Dion via
2022-08-26 6:40 ` Yasuaki Kudo
2022-10-12 9:55 ` Ade Malsasa Akbar
2022-10-12 10:18 ` Olivier Dion via
2022-08-26 7:24 ` Ricardo Wurmus
2022-08-31 1:42 ` Thompson, David
2022-08-31 6:33 ` Ricardo Wurmus
2022-08-31 10:46 ` [EXT] " Thompson, David
2022-08-31 11:42 ` Olivier Dion via
2022-08-31 12:54 ` Thompson, David
2022-09-05 19:38 ` [EXT] " Ludovic Courtès
2023-01-23 15:34 ` Giovanni Biscuolo [this message]
2023-01-23 16:48 ` declarative containers (was Re: [EXT] Re: Enterprise Guix Hosting?) Przemysław Kamiński
2023-01-23 17:59 ` Wojtek Kosior via
2022-09-05 19:42 ` Enterprise Guix Hosting? Ludovic Courtès
2022-10-07 11:03 ` zimoun
2022-10-08 16:23 ` Phil
2022-10-10 7:58 ` zimoun
2022-10-10 10:30 ` (
2022-10-10 10:49 ` zimoun
2022-10-10 19:35 ` Phil
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=87wn5dgt7m.fsf@xelera.eu \
--to=g@xelera.eu \
--cc=dthompson2@worcester.edu \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.org \
--cc=olivier.dion@polymtl.ca \
--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.
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).