I played with the log drivers (I’m on a very old Podman … 1.6.2). What a found was
journald didn’t use the file path at all. I used a less specific retrieval (along the
lines of just journalctl). It wasn’t satisfactory to me. Instead, I chose the k8s driver.
Despite the implications that this is somehow JSON-formatted output, it wasn’t. It wrote
my output to the file I requested as plain text.
On Jan 25, 2022, at 4:55 PM, Ranbir
I'm testing out using journald for logging from one of my containers. I
think I configured it correctly, but I don't see anything in the path I
passed to it.
Here's the create command I used:
/var/log/containers is empty:
# ls -l /var/log/containers/
Docker's docs on retrieving the logs with journalctl don't show me
-- Logs begin at Wed 2022-01-19 17:04:20 EST, end at Tue 2022-01-25
18:40:27 EST. --
-- No entries --
Incidentally, I used podman to crate the systemd unit files for the pod
and dumped them into /etc/systemd/system. I'm starting, stopping, etc
the pod using systemctl.
Using journald for logging means the container's logs get written to
the host's journal, right? If that's true, what am I doing wrong?
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io