Bug 1166076

Summary: Fedora 21 Atomic Image: docker service is not starting during boot as it is not enabled by-default
Product: [Fedora] Fedora Reporter: Lalatendu Mohanty <lmohanty>
Component: docker-ioAssignee: Colin Walters <walters>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 21CC: admiller, dwalsh, golang-updates, hushan.jia, jchaloup, jperrin, lsm5, lsm5, mattdm, mgoldman, miminar, s, thrcka, vbatts
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1166082 (view as bug list) Environment:
Last Closed: 2015-01-19 14:48:59 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:
Bug Depends On:    
Bug Blocks: 1166082    

Description Lalatendu Mohanty 2014-11-20 11:37:02 UTC
Description of problem:

Docker service is not starting during boot of Atomic image of Fedora 21 as it is not enabled in systemd.


bash-4.3# systemctl status docker
● docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled)
   Active: active (running) since Thu 2014-11-20 10:43:03 UTC; 47min ago
     Docs: http://docs.docker.com
 Main PID: 907 (docker)
   CGroup: /system.slice/docker.service
           └─907 /usr/bin/docker -d -H fd:// --selinux-enabled --storage-opt dm.fs=xfs --storage-opt dm.datadev=/dev/atomicos/docker-data --storage...


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

Fedora-Cloud-Atomic-20141112-21.x86_64.qcow2

How reproducible:

Always

Steps to Reproduce:
1. use  Fedora-Cloud-Atomic-20141112-21.x86_64.qcow2 to boot.
2. check if docker service is running
3.

Actual results:


Expected results:


Additional info:

Comment 1 Lokesh Mandvekar 2014-11-20 16:06:50 UTC
I'm guessing the enabling would be handled in the kickstart script or some appropriate place while the image is built, correct? Not sure if this needs changes to the docker rpm.

Comment 2 Daniel Walsh 2014-11-20 19:31:14 UTC
It would definitely not be in the docker package.

This should be enabled in the kickstart used to build the image.

I will let Colin assign it to someone.

Comment 3 Daniel Walsh 2015-01-19 14:48:59 UTC
I believe this is fixed in the current release, reopen if it continues to happen.