Hi, Antonio Carlos Padoan Junior <acpadoa...@yahoo.com.br> writes:
> I'm having a problem with guix system containers, but not sure if it a > bug or mis-configuration. I can't start postgres shepherd service > because system-log service is not starting. A permission issue on the > container: > > Status of system-log: > It is stopped (failing). > It is enabled. > Provides: system-log syslogd > Requires: root-file-system > Will not be respawned. > Failed to start at 14:40:52 (27 seconds ago). > root@container /# herd start system-log > herd: error: exception caught while executing 'start' on service 'system-log': > In procedure open-fdes: Operation not permitted The problem is that ‘system-log’ attempts to open /proc/kmsg, which fails (that’s not permitted in containers). Thus ‘system-log’ and everything that depends on it fails to start, making the system unusable. I’m preparing a patch in the Shepherd to simply ignore the error in that case, because I think it’s best to move on than to prevent the system from booting. In the meantime, you can use ‘modify-services’ to change the ‘kernel-log-file’ field of ‘system-log-configuration’ to #f. HTH! Ludo’.
