Jan Wielkiewicz <tona_kosmicznego_smie...@interia.pl> writes:

>> This means the daemon isn’t running.
>> 
>> If you use SELinux in enforcing mode then the daemon is probably
>> prevented from starting.
> I'm not aware of this - I just picked all default settings, not that
> the choice was big.

It’s not Guix, it’s Fedora.  Fedora ships with SELinux enabled by
default, which means that all software needs to have a policy that
declares in what context it runs and what other contexts it can access.

>> Sure.  We have a draft SELinux policy for systems like yours, but it
>> is probably no longer current as Fedora’s SELinux policy is not
>> frozen in time.  I encourage you to try it and help debug it to
>> adjust it for current versions of Fedora.
> That's my first day running Fedora, but if someone gives me right
> directions, I can help.

The first thing to do is to install the guix-daemon.cil file as
explained in the manual.  That file is part of the Guix source
repository.

Then as you start guix-daemon you need to look at
/var/log/audit/audit.log (or similar) to see why SELinux blocked the
daemon from running.

-- 
Ricardo

Reply via email to