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 1419485 - [RFE] Sanitize Docker Logging
Summary: [RFE] Sanitize Docker Logging
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.3
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Antonio Murdaca
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1186913
TreeView+ depends on / blocked
 
Reported: 2017-02-06 10:32 UTC by Marko Myllynen
Modified: 2021-03-11 14:56 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-19 14:50:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Marko Myllynen 2017-02-06 10:32:29 UTC 
Description of problem:
Starting docker on a new RHEL 7 installation and doing some basic operations (pull/tag/push) I see lots of completely unhelpful logging in system log, for example:

...
Feb  6 10:56:05 rhev-i24c-01 dockerd-current: time="2017-02-06T10:56:05.834973437+02:00" level=info msg="{Action=create, Username=root, LoginUID=0, PID=41739}"
Feb  6 10:56:07 rhev-i24c-01 dockerd-current: time="2017-02-06T10:56:07.685058729+02:00" level=info msg="{Action=create, Username=root, LoginUID=0, PID=41746}"
Feb  6 10:56:09 rhev-i24c-01 dockerd-current: time="2017-02-06T10:56:09.979106816+02:00" level=info msg="{Action=create, Username=root, LoginUID=0, PID=41768}"
...
Feb  6 10:59:00 rhev-i24c-01 dockerd-current: time="2017-02-06T10:59:00.653854710+02:00" level=info msg="{Action=remove, Username=root, LoginUID=0, PID=42750}"
Feb  6 10:59:01 rhev-i24c-01 dockerd-current: time="2017-02-06T10:59:01.034145787+02:00" level=info msg="{Action=tag, Username=root, LoginUID=0, PID=42757}"
Feb  6 10:59:01 rhev-i24c-01 dockerd-current: time="2017-02-06T10:59:01.855460794+02:00" level=info msg="{Action=push, Username=root, LoginUID=0, PID=42764}"
...
Feb  6 11:50:07 rhev-i24c-01 dockerd-current: time="2017-02-06T11:50:07.095448146+02:00" level=error msg="Not continuing with pull after error: unknown: Not Found"
...

I don't think messages like this belong to system log by default. Either not logging these or logging at warn level should be considered. Or perhaps create a separate log for docker. In any case, the last message is also an example of unhelpful logging, something wasn't found somewhere - if this must be logged then obviously "what" and "where" should be logged as well to make the message meaningful.

Also, on a busy docker host there's a huge amount of mounting/unmounting messages, not sure can anything by done to that in the context of docker.

These are just some quick examples, would be great to have docker logging reviewed and sanitized in general. If done in upstream/Fedora already, then please consider backporting to RHEL 7.

Thanks.

Version-Release number of selected component (if applicable):
docker-1.12.5-14.el7.x86_64
Comment 1 Marko Myllynen 2017-02-06 10:33:55 UTC 
See also:

https://bugzilla.redhat.com/show_bug.cgi?id=1419486
https://bugzilla.redhat.com/show_bug.cgi?id=1419487
Comment 3 Daniel Walsh 2017-06-30 15:02:22 UTC 
Antonio what do you want to do with this one?
Comment 4 Marko Myllynen 2017-08-10 12:04:57 UTC 
When testing with OCP 3.6 lines like these are printed thousands of times:

Aug 10 08:00:42 master01 oci-umount: umounthook <info>: Failed to canonicalize path [/var/lib/docker/overlay2]: No such file or directory. Skipping.
Aug 10 08:00:42 master01 oci-umount: umounthook <info>: Failed to canonicalize path [/var/lib/docker/overlay]: No such file or directory. Skipping.
Aug 10 08:00:42 master01 oci-umount: umounthook <info>: Failed to canonicalize path [/var/lib/docker-latest/overlay2]: No such file or directory. Skipping.
Aug 10 08:00:42 master01 oci-umount: umounthook <info>: Failed to canonicalize path [/var/lib/docker-latest/overlay]: No such file or directory. Skipping.
Aug 10 08:00:42 master01 oci-umount: umounthook <info>: Failed to canonicalize path [/var/lib/docker-latest/devicemapper]: No such file or directory. Skipping.
Aug 10 08:00:42 master01 oci-umount: umounthook <info>: Failed to canonicalize path [/var/lib/docker-latest/containers]: No such file or directory. Skipping.
Aug 10 08:00:42 master01 oci-umount: umounthook <info>: Failed to canonicalize path [/var/lib/container/storage/lvm]: No such file or directory. Skipping.
Aug 10 08:00:42 master01 oci-umount: umounthook <info>: Failed to canonicalize path [/var/lib/container/storage/devicemapper]: No such file or directory. Skipping.
Aug 10 08:00:42 master01 oci-umount: umounthook <info>: Failed to canonicalize path [/var/lib/container/storage/overlay]: No such file or directory. Skipping.

This is counter-productive, please avoid such log pollution. Thanks.
Comment 5 Simon Reber 2017-09-11 12:55:23 UTC 
(In reply to Marko Myllynen from comment #4)
> When testing with OCP 3.6 lines like these are printed thousands of times:
> 
> Aug 10 08:00:42 master01 oci-umount: umounthook <info>: Failed to
> canonicalize path [/var/lib/docker/overlay2]: No such file or directory.
> Skipping.
> Aug 10 08:00:42 master01 oci-umount: umounthook <info>: Failed to
> canonicalize path [/var/lib/docker/overlay]: No such file or directory.
> Skipping.
> Aug 10 08:00:42 master01 oci-umount: umounthook <info>: Failed to
> canonicalize path [/var/lib/docker-latest/overlay2]: No such file or
> directory. Skipping.
> Aug 10 08:00:42 master01 oci-umount: umounthook <info>: Failed to
> canonicalize path [/var/lib/docker-latest/overlay]: No such file or
> directory. Skipping.
> Aug 10 08:00:42 master01 oci-umount: umounthook <info>: Failed to
> canonicalize path [/var/lib/docker-latest/devicemapper]: No such file or
> directory. Skipping.
> Aug 10 08:00:42 master01 oci-umount: umounthook <info>: Failed to
> canonicalize path [/var/lib/docker-latest/containers]: No such file or
> directory. Skipping.
> Aug 10 08:00:42 master01 oci-umount: umounthook <info>: Failed to
> canonicalize path [/var/lib/container/storage/lvm]: No such file or
> directory. Skipping.
> Aug 10 08:00:42 master01 oci-umount: umounthook <info>: Failed to
> canonicalize path [/var/lib/container/storage/devicemapper]: No such file or
> directory. Skipping.
> Aug 10 08:00:42 master01 oci-umount: umounthook <info>: Failed to
> canonicalize path [/var/lib/container/storage/overlay]: No such file or
> directory. Skipping.
> 
> This is counter-productive, please avoid such log pollution. Thanks.
My customer is reporting the same messages after updated to Red Hat OpenShift Container Platform 3.4 and Red Hat Enterprise Linux 7.4.

We should definitely try to avoid this kind of messages as it's filling up log files.
Comment 6 Derrick Ornelas 2019-09-19 14:50:28 UTC 
With the start of the Maintenance Support 1 phase[1] on August 6, 2019 no new software functionality is planned for Red Hat Enterprise Linux 7.  As docker is not available in Red Hat Enterprise Linux 8 it is not possible to re-evaluate this request for the next release.  


[1] https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_1_Phase
Note You need to log in before you can comment on or make changes to this bug.