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. > I think I've used the emacs-guix package to see the dependency graphs > of services and that helped me IIRC. Plus peaking in the services > source code. I tried that but I am not enough of a low-level Linux expert to get much benefit from it. What I did notice is that syslogd is actually running once it has been started. It shows up in 'ps', and /var/log/messages keeps accumulating entries. /var/run/syslog.pid exists and contains the pid of the running syslogd process. 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 :-( Konrad.
