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 1328917 - Problem upgrading from Docker 1.8.2 to 1.9.1: "Could not find container for entity id"
Summary: Problem upgrading from Docker 1.8.2 to 1.9.1: "Could not find container for e...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Antonio Murdaca
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-20 14:52 UTC by Brenton Leanhardt
Modified: 2019-03-06 02:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-23 16:18:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1274 0 normal SHIPPED_LIVE docker bug fix and enhancement update 2016-06-23 20:12:28 UTC

Description Brenton Leanhardt 2016-04-20 14:52:58 UTC 
Description of problem:
As best I can tell this is the exact problem mentioned here:

https://github.com/docker/docker/issues/17691

Editing the sqlite db as mentioned in the issue worked around the problem for me:

sudo sqlite3 /var/lib/docker/linkgraph.db
delete from edge where entity_id = '<conflicting-entity-id-sha-1>';
delete from entity where id = '<conflicting-entity-id-sha-1>';

Version-Release number of selected component (if applicable):

docker-1.9.1-25.el7.x86_64

How reproducible:

I've hit this randomly.  Our openvswitch container is launched by systemd and effectively runs this command:

/usr/bin/docker run --name openvswitch --rm --privileged --net=host --pid=host -v /lib/modules:/lib/modules -v /run:/run -v /sys:/sys:ro -v /etc/origin/openvswitch:/etc/openvswitch openshift3/openvswitch:v3.2.0.12

Actual results:

Error response from daemon: Could not find container for entity id a1ad40523b86be16092de9384175b23bc6c8b92a1744c7783b7315c375a9a877


Expected results:


Additional info:
Comment 2 Daniel Walsh 2016-04-21 04:46:05 UTC 
Not sure how we would fix this, other then to release onte it.

Would rm -f /var/lib/docker/linkgraph.db  Have worked?
Comment 3 Brenton Leanhardt 2016-04-21 11:52:10 UTC 
I'm happy to try that the next time I hit this.  How safe it is to do that when upgrading from docker 1.8.2 to 1.9.1?  How is the linkgraph rebuilt?
Comment 4 Daniel Walsh 2016-04-22 18:21:16 UTC 
I believe it is rebuilt from the existing graph driver.
Comment 5 Daniel Walsh 2016-06-03 18:24:35 UTC 
Fixed in docker-1.9
Comment 7 Luwen Su 2016-06-12 15:00:00 UTC 
I tried serveral times to start and stop the container, it works fine docker-1.10.3-40.el7.x86_64:
# docker run --name openvswitch --rm --privileged --net=host --pid=host -v /lib/modules:/lib/modules -v /run:/run -v /sys:/sys:ro -v /etc/origin/openvswitch:/etc/openvswitch openshift3/openvswitch
Starting ovsdb-server.
Configuring Open vSwitch system IDs.
Starting ovs-vswitchd.
Enabling remote OVSDB managers.

#docker ps
 IMAGE                    COMMAND                  CREATED             STATUS              PORTS               NAMES
9687cb843d31        openshift3/openvswitch   "/usr/local/bin/ovs-r"   36 seconds ago      Up 34 seconds                           openvswitch


I used to met this issue long time ago and use removing linkgraph.db to workaround as same, but i've been a while not seen this.
If anyone meet this with latest docker version, feel free reopen this bug.
Comment 9 errata-xmlrpc 2016-06-23 16:18:16 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.