unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alexey Abramov <levenson@mmer.org>
To: "Ludovic Courtès" <ludo@gnu.org>, "Ricardo Wurmus" <rekado@elephly.net>
Cc: <guix-devel@gnu.org>, <goodoldpaul@autistici.org>
Subject: Re: OCI-backed Guix System Services
Date: Mon, 02 Oct 2023 18:54:04 +0200	[thread overview]
Message-ID: <18af14fa7e0.280a.da5dc967fe079fb386b94d5b80162893@mmer.org> (raw)
In-Reply-To: <87v8bphyah.fsf@gnu.org>


I am playing with Talos right now, which is a Kubernetes Linux 
distribution. It doesn't provide any ssh access. You can configure it using 
api only.

I am wondering if anyone wants to work (or working) on similar thing using 
Guix, Shepherd and Goblins.

It would be great to just boot guix with shepherd and program the system 
using scheme.

I haven't tested swineherd yet though.

On October 2, 2023 4:52:57 PM Ludovic Courtès <ludo@gnu.org> wrote:

> Hi,
>
> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>>> I was recently inspired from Nix's oci-container feature and wrote a thin 
>>> wrapper around the docker CLI to enable the management of
>>> docker containers through Shepherd [0]. This enables handling of non 
>>> packaged services through guix system reconfigure and herd
>>> start/stop/status .
>>
>> Neat!
>>
>>> To conclude, I'm not advocating for adding OCI-backed services to Guix 
>>> mainstream: in my opinion they should be bootstrapped and
>>> built from source, but I believe the actual "backend" implementation for 
>>> such services could be useful to have in Guix. What do you
>>> think?
>>
>> I think this could still be a valuable addition to Guix, because it
>> integrates with Shepherd and thus unifies management of system services
>> independent of whether they came from Guix or from elsewhere.
>
> I agree, this would be useful to many people I’m sure, in particular to
> anyone who doesn’t dare switch to Guix System out of fear of not finding
> a specific service.
>
> If there’s a way this could be generalized so others can use it for
> daemons other than Grafana, that’d be great.
>
> Ludo’.





      reply	other threads:[~2023-10-02 16:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20 14:47 OCI-backed Guix System Services paul
2023-09-20 22:12 ` Ricardo Wurmus
2023-09-20 23:10   ` Katherine Cox-Buday
2023-09-22 15:23   ` paul
2023-10-02 14:52   ` Ludovic Courtès
2023-10-02 16:54     ` Alexey Abramov [this message]

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=18af14fa7e0.280a.da5dc967fe079fb386b94d5b80162893@mmer.org \
    --to=levenson@mmer.org \
    --cc=goodoldpaul@autistici.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --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.
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).