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:
To stop a running container using docker kill and atomic stop command, which will take 10 times real time than docker kill.
Version-Release number of selected component (if applicable):
# rpm -q docker atomic
docker-1.9.1-11.el7.x86_64
atomic-1.8-2.gita35ae18.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1. atomic run rhel7/rhel-tools
2. time docker kill <container_id>
3. repeat 1
4. time atomic stop <container_id>
Actual results:
# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
04e682b4026f rhel7/rhel-tools "/usr/bin/bash" 12 days ago Up 5 seconds rhel-tools
# time docker kill 04e682b4026f
04e682b4026f
real 0m0.153s
user 0m0.025s
sys 0m0.007s
# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
04e682b4026f rhel7/rhel-tools "/usr/bin/bash" 12 days ago Up 2 seconds rhel-tools
# time atomic stop 04e682b4026f
real 0m10.266s
user 0m0.105s
sys 0m0.025s
Expected results:
Fix it.
Additional info:
(In reply to Daniel Walsh from comment #2)
> atomic stop is doing a docker stop not a docker kill.
Yes, I just double check it, the Atomic stop will call docker.Client.stop method, and there is no big time deviation between atomic stop and docker stop.
[cloud-user@atomic-00 ~]$ time sudo docker stop f86ba0e9290a
f86ba0e9290a
real 0m10.100s
user 0m0.018s
sys 0m0.011s
[cloud-user@atomic-00 ~]$ time sudo atomic stop f86ba0e9290a
real 0m10.614s
user 0m0.435s
sys 0m0.030s