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.

Created attachment 1135449 [details]
reproducer script: create in-use image, try to rmi it by hash

Using: docker-1.9.1-el7

'docker rmi' of an in-use image will fail (correctly) but will erase an associated image name, leaving it as <none>:

    $ docker images     [edited for legibility]
    foo     latest      f129792fbded   1 seconds ago       194.6 MB

    $ docker rmi f129792fbded
    Error response from daemon: conflict: unable to delete f129792fbded (cannot be forced) - image is being used by running container c1f1084111e5
    Error: failed to remove images [f129792fbdedc0357363361668bb8a7e63096c06bd99ae94b82397d3490186be]

    $ docker images     [edited for legibility]
    <none>  <none>      f129792fbded   4 seconds ago       194.6 MB

 See attached reproducer script.

I tried this on docker upstream. This is fixed in docker latest (upstream/master) branch.

Ed, 

Can you try it on docker 1.10 and see if it's fixed there ?

Shishir

I cannot reproduce on docker-latest-1.10.3-22.el7. Tried manually, with reproducer script, and with docker-autotest. All gave the desired behavior.

I know there's a -26 out but I haven't installed it on my test setup. I will be on PTO until June 20 and will not be able to do further tests.

Fixed in Docker 1.10.
Moving this to modified.

Shishir

(In reply to Ed Santiago from comment #3)
> I cannot reproduce on docker-latest-1.10.3-22.el7. Tried manually, with
> reproducer script, and with docker-autotest. All gave the desired behavior.
> 
> I know there's a -26 out but I haven't installed it on my test setup. I will
> be on PTO until June 20 and will not be able to do further tests.

works well with the -40 version, move to verified

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, 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/RHBA-2016:1274