unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>, guix-devel@gnu.org
Subject: Re: syslogd can't be started when running Guix in Docker
Date: Thu, 04 Jul 2019 17:39:15 +0200	[thread overview]
Message-ID: <m18stdajx8.fsf@fastmail.net> (raw)
In-Reply-To: <20FC714B-1D75-4D36-B24F-DECFEE257350@gmail.com>

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

> I'm happy to read you could successfully make it work! It's strange
> that you had that issue though!

By now I have a system that starts all services without failure. I got
there by increasing the timeout to 30 s everywhere (compared to the
default value of 5). Perhaps 30 is more than necessary, I didn't try
intermediate values. So it looks like Guix in Docker is a bit slow to
boot, at least on the Mac.

A more fundamental question is whether I will be able to do useful work
with this setup. It is well known that host file access from Docker on
macOS is slow, but I didn't realize how slow it is until I compiled Guix
in... four hours. On the same machine booted to Linux, it's about 40
minutes.

Konrad.

  reply	other threads:[~2019-07-04 15:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-02 17:16 syslogd can't be started when running Guix in Docker Konrad Hinsen
2019-07-03  5:10 ` Maxim Cournoyer
2019-07-03  8:12   ` Konrad Hinsen
2019-07-03 11:17     ` Konrad Hinsen
2019-07-04 13:10       ` Maxim Cournoyer
2019-07-04 15:39         ` Konrad Hinsen [this message]
2019-07-05 18:22           ` Maxim Cournoyer
2019-07-05 22:25           ` Ludovic Courtès
2019-07-06  6:26             ` Konrad Hinsen
2019-07-11 15:35               ` Ludovic Courtès
2019-07-11 18:40                 ` Konrad Hinsen
2019-07-11 21:00                   ` 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=m18stdajx8.fsf@fastmail.net \
    --to=konrad.hinsen@fastmail.net \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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).