Open SpComb opened 6 years ago
Somewhat mitigated by the /*/log/journal
being optional... if neither is mounted to the container, then the systemd execs will simply not read anything from the journal.
I suppose we could just omit the journal mounts from the daemonset, but it would mean that you need to manually journalctl -u host-upgrades
on the host to debug exec errors...
The transient
/run/log/journal
directory will not exist if the persistent/var/log/journal
directory has been setup, and this causes the volume mounts for the pod to fail. I don't know if it's possible to mount both journal paths for the daemonset without interfering with the systemd-journald operation by creating the/var/log/journal
directory as a side-effect. This makes pod/container access to the host journal problematic, given the lack of a dbus API for journald... This might make the use of systemd for execs a bad idea, since it relies on journal access for the output logging functionality.