Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Even though we can change the logging drivers for podman using --log-driver but we cannot set the configs for them. --log-opt option values is not taken up by podman.
E;g for json-file and k8s-file max-file and max-size cannot be set.
"HostConfig": {
"ContainerIDFile": "",
"LogConfig": {
"Type": "k8s-file",
"Config": {}
},
"HostConfig": {
"ContainerIDFile": "",
"LogConfig": {
"Type": "json-file",
"Config": {}
},
Version-Release number of selected component (if applicable):
podman-1.4.4-4.el7.x86_64
Additional info:
https://github.com/containers/libpod/pull/1773
Any updates after above changes ?
Podman supports a (limited) set of log drivers, but does not presently support setting options for these drivers. Are there any specific options that you want to use?
We might be able to do something here, but realize that we don't have a long running daemon, unless conmon could handle this. I guess max-size and max-files would rename the existing log file to annother name and then start writing a new log file. Then if we had three renames, would remove the oldest.
This seems to work somewhat
./bin/podman run -d --log-opt max-size=1m alpine sleep 500
Which passes to conmon the
--log-size-max 1000000
flag.
I don't believe this is perfect, but it does satisfy the requirement.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: container-tools:rhel8 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2021:1796
Description of problem: Even though we can change the logging drivers for podman using --log-driver but we cannot set the configs for them. --log-opt option values is not taken up by podman. E;g for json-file and k8s-file max-file and max-size cannot be set. "HostConfig": { "ContainerIDFile": "", "LogConfig": { "Type": "k8s-file", "Config": {} }, "HostConfig": { "ContainerIDFile": "", "LogConfig": { "Type": "json-file", "Config": {} }, Version-Release number of selected component (if applicable): podman-1.4.4-4.el7.x86_64 Additional info: https://github.com/containers/libpod/pull/1773 Any updates after above changes ?