Currently, docker daemon runtime has a default --log-driver set
to journald.
Podman lack of daemon prevent such a global application, meaning
we have to set that driver for each and every container when we
either create or run them.
Notes:
- podman only supports "json-file", and it's not even a json.
- docker json-file doesn't support "path" option, making this output
unusable in the end: logs end in
/var/lib/docker/containers/ID/ID-json.log
Reviewed: https:/ /review. openstack. org/635438 /git.openstack. org/cgit/ openstack/ paunch/ commit/ ?id=fba5e04fdd1 fa9ed85f02f1dab 0794e1f4828739
Committed: https:/
Submitter: Zuul
Branch: master
commit fba5e04fdd1fa9e d85f02f1dab0794 e1f4828739
Author: Cédric Jeanneret <email address hidden>
Date: Wed Feb 6 14:05:11 2019 +0100
Inject log-driver for podman containers
Currently, docker daemon runtime has a default --log-driver set
to journald.
Podman lack of daemon prevent such a global application, meaning
we have to set that driver for each and every container when we
either create or run them.
Notes: var/lib/ docker/ containers/ ID/ID-json. log
- podman only supports "json-file", and it's not even a json.
- docker json-file doesn't support "path" option, making this output
unusable in the end: logs end in
/
Related-Bug: #1814897 73a77b624f5350c 424d4c3030a
Change-Id: I7ac10a9b42ecae