all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Wojtek Kosior via <help-guix@gnu.org>
To: Felix Lechner via <help-guix@gnu.org>
Cc: Felix Lechner <felix.lechner@lease-up.com>, Benjamin <benjamin@uvy.fr>
Subject: Re: Running guix system services only
Date: Fri, 8 Dec 2023 16:46:40 +0100	[thread overview]
Message-ID: <20231208164640.5ce8e6e9.koszko@koszko.org> (raw)
In-Reply-To: <87wmtokd7a.fsf@lease-up.com>

[-- Attachment #1: Type: text/plain, Size: 3156 bytes --]

Hi all!

> On Tue, Nov 21 2023, Benjamin wrote:
> 
> > I am trying to transfer smoothly from a standard Debian to a Guix system
> > on one of my servers.  
> 
> I would recommend to migrate to a new Guix server instead and use your
> DNS or other configuration methods to coordinate between the two. That's
> what I did, from Debian stable, about a year and a half ago.

I just noticed this thread — this is more or less the problem I am
trying to deal with.  On my VPS running Debian I moved most of my
services into a Guix container.  The directories with important state
(e.g. user homes with Maildirs inside, gitolite repositories, some
static files being served over HTTP) are shared with the host.  User
ids of some daemons inside the container are set to be the same as
outside.

The container communicates with the outside world through a veth pair.
The host has some internet-facing ports forwarded to the container.  If
you're curious, here[1] is the code that spins up the container.  It is
called from an init script (managed by systemd but the script itself is
sysV-compatible).

The overall result is somewhat messy and I would like to already have
everything running under a full Guix system.  Meanwhile, I've been
stuck in this transition for over a year now — it's probably just as
inconvenient as insecure.

A full system would allow one to utilize
- the unatended-upgrade-service-type
- and the `guix deploy` command.

So — to all who are yet to do such a migration — my suggestion would be
not to set up a Guix container the way I did it.  If you have a second
server — Felix' approach is probably the best.  Otherwise, a VM with
Guix inside could be a a more practical solution than containers — as
long as the server you're going to run it on has enough RAM

Best :)
Wojtek


-- (sig_start)
website: https://koszko.org/koszko.html
fingerprint: E972 7060 E3C5 637C 8A4F  4B42 4BC5 221C 5A79 FD1A
follow me on Fediverse: https://friendica.me/profile/koszko/profile

♥ R29kIGlzIHRoZXJlIGFuZCBsb3ZlcyBtZQ== | ÷ c2luIHNlcGFyYXRlZCBtZSBmcm9tIEhpbQ==
✝ YnV0IEplc3VzIGRpZWQgdG8gc2F2ZSBtZQ== | ? U2hhbGwgSSBiZWNvbWUgSGlzIGZyaWVuZD8=
-- (sig_end)


On Fri, 08 Dec 2023 05:59:05 -0800 Felix Lechner via <help-guix@gnu.org> wrote:

> Hi Benjamin,
> 
> On Tue, Nov 21 2023, Benjamin wrote:
> 
> > I am trying to transfer smoothly from a standard Debian to a Guix system
> > on one of my servers.  
> 
> I would recommend to migrate to a new Guix server instead and use your
> DNS or other configuration methods to coordinate between the two. That's
> what I did, from Debian stable, about a year and a half ago.
> 
> The Guix part was very painful for me, but I turned off the Debian
> server after four weeks. I am still learning about Guix but have reached
> a point where I am comfortable trying to contribute.
> 
> Guix is an amazing package manager (and distribution) that runs much
> more stable than anything I've used in the past. The learning curve is
> brutal but was totally worth it!
> 
> IRC is your friend.
> 
> Kind regards
> Felix
> 

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-12-08 15:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21 16:47 Running guix system services only Benjamin
2023-12-08 13:59 ` Felix Lechner via
2023-12-08 15:46   ` Wojtek Kosior via [this message]
2023-12-08 17:38 ` Simon Tournier

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=20231208164640.5ce8e6e9.koszko@koszko.org \
    --to=help-guix@gnu.org \
    --cc=benjamin@uvy.fr \
    --cc=felix.lechner@lease-up.com \
    --cc=koszko@koszko.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.