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.

Bug 1873228

Summary:	podman run --log-driver json-file didn't works as expect
Product:	Red Hat Enterprise Linux 8	Reporter:	Joy Pu <ypu>
Component:	podman	Assignee:	Tom Sweeney <tsweeney>
Status:	CLOSED DUPLICATE	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.3	CC:	bbaude, dwalsh, jligon, jnovy, lsm5, mheon
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-08-27 19:38:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Joy Pu 2020-08-27 16:46:09 UTC

Description of problem:
podman run --log-driver json-file didn't work as expect. When set log driver to json-file, podman logs can not get the logs as expect.

Version-Release number of selected component (if applicable):
podman-2.0.4-3.module+el8.3.0+7716+ce654703.x86_64

How reproducible:


Steps to Reproduce:
1. start a container with --log-driver json-file
# podman run --log-driver json-file --log-opt path=/tmp/podman-jsonfile.log ubi8 echo test
test

2. Check if the string is write to the file
# cat /tmp/podman-jsonfile.log

2. Use podman logs to check if we can get the logs from journald
# podman ps -a
CONTAINER ID  IMAGE                                   COMMAND               CREATED         STATUS                     PORTS   NAMES
310ce542ccb0  registry.access.redhat.com/ubi8:latest  echo test             23 seconds ago  Exited (0) 20 seconds ago          quirky_wilson
# podman  logs 310ce542ccb0


Actual results:
in step 2 it report no such file
in step 3 there is nothing in the output

Expected results:
log file should exist and podman logs should can get the string echo from run.

Additional info:

Comment 1 Tom Sweeney 2020-08-27 19:38:08 UTC

This looks to be an exact duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1873204.  As such I'm closing this one as 1873204 has some ongoing comments already and this one does not.  Joy if you disagree, please reopen and note how this differs.

*** This bug has been marked as a duplicate of bug 1873204 ***