Konrad Hinsen skribis:
> Ludovic Courtès writes:
>
>> Do you observe similar slowness with other Docker images—e.g., Debian
>> images?
>
> No. But I don't observe any slowness with Guix either. Once it's up and
> running, performance is normal (except for the known problem with access
> to macOS
Ludovic Courtès writes:
> Do you observe similar slowness with other Docker images—e.g., Debian
> images?
No. But I don't observe any slowness with Guix either. Once it's up and
running, performance is normal (except for the known problem with access
to macOS file systems). It's only the daemon
Konrad Hinsen skribis:
>> Five seconds to spawn a process is already relatively long; we could
>> increase it a little, but the slowness here is a concern.
>
> Whereas the problems with file access are known and understood
> (ultimately it is the important differences in low-level file handling
>
Hi Ludo,
>> 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 a
Hi,
Konrad Hinsen skribis:
> Maxim Cournoyer 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 (compa
Hello!
Konrad Hinsen writes:
> Maxim Cournoyer 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 (com
Maxim Cournoyer 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
Hi Konrad!
I'm happy to read you could successfully make it work! It's strange that you
had that issue though!
Cheers,
Maxim
On July 3, 2019 11:17:03 AM UTC, Konrad Hinsen
wrote:
>On 03/07/2019 10:12, Konrad Hinsen wrote:
>
>> All this suggests that perhaps the problem is not with syslogd, b
On 03/07/2019 10:12, Konrad Hinsen wrote:
All this suggests that perhaps the problem is not with syslogd, but with
shepherd wrongly concluding that syslogd failed.
Looks like I will have to dig a bit more into shepherd :-(
My hypothesis turned out to be correct: increasing the timeout was
su
Hi Maxim,
Thanks for your reply!
> Try running the Docker container in privileged mode (docker run
> --privileged); I think this will allow the necessary Guix services
> dependencies of the syslog service to run.
I am already running in priviledged mode. Without it, I couldn't
build packages.
>
Hi Konrad,
On July 2, 2019 5:16:40 PM UTC, Konrad Hinsen
wrote:
>Hi everyone,
>
>I am exploring the possibility of running Guix under macOS via Docker.
>First I ran 'guix system docker-image` on a minimal system
>configuration, which I then transferred to the Mac and started.
>Overall it works a
Hi everyone,
I am exploring the possibility of running Guix under macOS via Docker.
First I ran 'guix system docker-image` on a minimal system
configuration, which I then transferred to the Mac and started.
Overall it works admirably well. There are however a few services
that don't work, in parti
12 matches
Mail list logo
