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.

Bug 1462020

Summary: docker service unusable if container-engine has ever run on host
Product: Red Hat Enterprise Linux 7 Reporter: Ed Santiago <santiago>
Component: rhel7-container-engine-dockerAssignee: Jhon Honce <jhonce>
Status: CLOSED DUPLICATE QA Contact: Martin Jenner <mjenner>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4Keywords: Extras
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-26 18:50:26 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 Ed Santiago 2017-06-15 22:38:09 UTC
Created attachment 1288206 [details]
output of systemctl status docker after the last two docker info commands

The act of 'systemctl start container-engine', even once, makes any subsequent 'systemctl start docker' run an unusable docker daemon.

    # systemctl disable --now docker
    Removed symlink /etc/systemd/system/multi-user.target.wants/docker.service.
    # atomic install --system --system-package=no --name container-engine [IMG]
    [succeeds]

container-engine has been installed but never run. docker still works:

    # systemctl start docker
    # docker info
    [succeeds]

Stop docker, switch to container-engine:

    # systemctl stop docker;systemctl start container-engine
    # docker info
    [succeeds]

Switch back to docker:

    # systemctl stop container-engine;systemctl start docker
    # docker info
    [15-second pause]
    Error response from daemon: plugin rhel-push-plugin failed with error: plugin not found

Subsequent attempts fail differently:

    # docker info
    An error occurred trying to connect: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.24/info: EOF

systemctl status docker reports it still running  and active, but with a panic. See attachment.

I have not yet found a way to get plain docker working again. The obvious first thing to try was rm -rf /run/docker* /run/containerd.sock; it has no effect. rpm -V docker docker-client docker-common docker-rhel-push-plugin reports only /etc/sysconfig/docker* and /var/lib/docker (expected).

Comment 2 Jhon Honce 2017-06-16 17:19:35 UTC
What are the NVM of the docker rpm's on the system?  The plugin rpm as well.  Thanks.

Comment 3 Ed Santiago 2017-06-16 19:55:05 UTC
docker-1.12.6-39.1.git6ffd653.el7.x86_64

rhel-push-plugin is the same. I don't think it's possible to install docker-x  with docker-rhel-push-plugin-y: it's an rpm "=" dependency.

rhel-push-plugin is fine, incidentally: 

    # rpm -V docker-rhel-push-plugin
    [no output]

    # ls -lZ /usr/libexec/docker/rhel-push-plugin
    -rwxr-xr-x. root root system_u:object_r:container_runtime_exec_t:s0 /usr/libexec/docker/rhel-push-plugin

    # atomic version $IMG
    IMAGE NAME                        VERSION   IMAGE ID  
    [...]container-engine:latest      1.12.6-4  7d4eccca7dfc

Comment 4 Jhon Honce 2017-07-26 18:50:26 UTC

*** This bug has been marked as a duplicate of bug 1367847 ***