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.
Docker logs flooded with warning level message cleanup: failed to unmount secrets: invalid argument; containerd: deleting container" error="exit status 1: \"container does not exist\\none or
Description of problem:
The following two error messages are repeated in the logs:
dockerd-current[1467]: time="2019-04-04T16:05:04.37673106-04:00" level=error msg="containerd: deleting container" error="exit status 1: \"container 53efb4402c22135d7bfbaf1d2a7e8529175341ff83e7bf0b6ebdd56aa87cb070 does not exist\\none or more of the container deletions failed\\n\""
dockerd-current[1467]: time="2019-04-04T16:05:04.494535464-04:00" level=warning msg="53efb4402c22135d7bfbaf1d2a7e8529175341ff83e7bf0b6ebdd56aa87cb070 cleanup: failed to unmount secrets: invalid argument"
Version-Release number of selected component (if applicable):
docker-1.13.1-68.gitdded712.el7.x86_64 (I was also sucessfull in reproducing on docker 1.13.1-94)
How reproducible:
Very
Steps to Reproduce:
1. stop a running docker container
2. check logs for the above messages
3.
Actual results:
The two above error messages are repeated in journal logs
Expected results:
No warning/error messages
Additional info:
I have seen this in every iteration of docker, and it seems very common. Is this a bug?
I have another open support ticket where the customer is also reporting the docker service logs outputting handler errors with "No such container" quite often, where it is filling up the docker logs. The pods themselves are starting just fine, but the error logs for No such container appear in the time the pods are in ContainerCreating state. In the same manner which was initially reported on this Bugzilla ticket, I believe the actual error is entirely normal and short-lived (the time it takes to actually create the container). However, the customer is complaining that since this event is logged as an error rather than info or warn, it makes it difficult to suppress it while maintaining other error level logs in docker.
The logs for docker service are filled with the following error during runtime:
dockerd-current: time="2019-05-31T11:05:56.654828821Z" level=error msg="Handler for GET /containers/e6789e99ac878346dcd9f9924a23d0e04ac142043ba0f2ebd3b82d63c9549347/json returned error: No such container: e6789e99ac878346dcd9f9924a23d0e04ac142043ba0f2ebd3b82d63c9549347"
I don't see any customer related data in the public comments of this bugzilla so I'm removing the redhat group and making the bugzilla public. We are an OpenSource company. Please work issues in the open.
Thanks,
Andreas
Comment 12Abdallah BENBRAHIM
2021-08-11 12:33:23 UTC
If you use a CIFS client, I invite you to check the CIFS driver deployed on your node.
Review the unmount function, make sure you remove the CREDENTIALS_FILE.