Bug 1318901

Summary:	Atomic Enterprise Platform is missing 'daemon' from ExecStart docker unit file
Product:	OpenShift Container Platform	Reporter:	Jason Shepherd <jshepherd>
Component:	Containers	Assignee:	Lokesh Mandvekar <lsm5>
Status:	CLOSED NOTABUG	QA Contact:	DeShuai Ma <dma>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.1.0	CC:	aos-bugs, jokerman, jshepherd, lsm5, miabbott, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-31 03:32:07 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:

Description Jason Shepherd 2016-03-18 05:32:42 UTC

Description of problem:

When trying to start docker on RHEL Atomic Host 7.2 2-2 docker fails to start.

ExecStart line in '/etc/systemd/system/docker.service' should including the work daemon ie:

'ExecStart=/usr/bin/docker daemon $OPTIONS'

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

7.2 2-2

How reproducible:

Try to start the docker daemon with 'systemctl start docker'


Actual results:

Error in Journalctl stating that --add-registry must come after daemon

Expected results:

Docker starts without error

Additional info:

I also had to manually remove the docker-pool logical volume then run 'docker-torage-setup' again after installation.

Comment 1 Lokesh Mandvekar 2016-03-22 18:38:51 UTC

shouldn't it be /usr/lib/systemd/system/docker.service

Comment 2 Lokesh Mandvekar 2016-03-22 18:40:41 UTC

also just checking, is ostree up to date on this machine?

Comment 3 Jason Shepherd 2016-03-22 23:23:36 UTC

I ran atomic host upgrade again today, and I remain on 7.2.2-2.

I see there also seems to be a Systemd Unit under /usr/lib/systemd/system. Changing the one under /etc/systemd/system had the affect of modifying the unit for me. I could see the affect of my changes when running 'systemctl start docker'.

Comment 4 Lokesh Mandvekar 2016-04-02 04:45:49 UTC

I'm not quite sure where you got the /etc/systemd/system/docker.service from. It shouldn't be present on a default/clean install. The default unitfile is (and should be) found in /usr/lib/systemd/system. Could you please check if /etc/systemd/system/docker.service occurs on a clean install?

Comment 5 Lokesh Mandvekar 2016-05-25 14:26:44 UTC

Hi Jason, do you still see this bug? Also, could you give me the steps to reproduce this on a clean atomic host?

Comment 6 Jason Shepherd 2016-05-31 03:32:07 UTC

I reinstalled, and seems to work fine on the second attempt