https://bugzilla.redhat.com/show_bug.cgi?id=1119413
Bug ID: 1119413
Summary: docker-io systemd unit file specifies environment
file. But, does not uses it.
Product: Fedora
Version: 20
Component: docker-io
Assignee: lsm5(a)switzerlandmail.ch
Reporter: prudhvi(a)mapr.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
hushan.jia(a)gmail.com, lsm5(a)switzerlandmail.ch,
mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io,
vbatts(a)redhat.com
Description of problem:
docker-io package installs docker.service systemd unitfile that uses
EnvironemtFile (/etc/sysconfig/docker). But, does not uses it on ExecStart.
For our use case we run docker with special storage options to increase the
default rootfs size on the container to 30GB. To do that we have to specify
additional command line flags to the docker daemon (--storage-opt
dm.basesize=30G --storage-opt dm.loopdatasize=200G).
Having to edit ExecStart on every docker-io package update does not scale. This
bug requests the use of Environment flags defined in (/etc/sysconfig/docker) to
be used on the ExecStart command line.
How reproducible:
Always
Steps to Reproduce:
1. Install docker-io
2. Specify additional command line flags in environment file and start service
3. The service doesn't start with the given flags.
Actual results:
Service doesn't start with correct command line flags
Expected results:
Service starts with correct command line falgs.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.