Bug 1258889

Summary: can't remove image by specifying its ID
Product: Red Hat Enterprise Linux 7 Reporter: Michal Minar <miminar>
Component: dockerAssignee: Lokesh Mandvekar <lsm5>
Status: CLOSED CURRENTRELEASE QA Contact: atomic-bugs <atomic-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: dwalsh, lsm5, lsu, mjenner, sghosh
Target Milestone: rcKeywords: Extras, Regression
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-07 21:50:53 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 Michal Minar 2015-09-01 13:12:49 UTC 
Description of problem:
  This is a regression of bz#1209576 [2]

Version-Release number of selected component (if applicable):
  docker-1.7.1-115.el7

How reproducible:
  Hardly

Steps to Reproduce:
1. use docker - pull images, build new ones, start containers
2. try to remove any image by its ID (docker rmi 54bdc57505af)

Actual results:
  Image isn't removed with this error:
  Error response from daemon: could not find image: Prefix can't be empty

Expected results:
  Image is removed.

Additional info:
  Already fixed in docker-1.6.2-8.el7 with a patch [1] merged upstream. The patch did not make it pass a rebase to 1.7.

[1] https://github.com/docker/docker/commit/71a499022904e1da074ded3e1ed874c1b75ccf23
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1209576
Comment 3 Michal Minar 2015-09-01 13:33:13 UTC 
Here's a PR with backported fix for 1.7: https://github.com/rhatdan/docker/pull/115
Comment 4 Daniel Walsh 2015-09-02 12:26:06 UTC 
I update the rhel7-1.7 branch with this fix.  Did we miss the window to get this into the next RHEL release?
Comment 5 Daniel Walsh 2015-09-02 12:27:43 UTC 
https://github.com/docker/docker/issues/12487
Is discussing this issue.
Comment 6 Daniel Walsh 2015-09-29 13:20:50 UTC 
Fixed in docker-1.8.2