DOCKER_OPTS do not work in config file /etc/default/docker #9889

seanlook · Jan 4, 2015

I have changed /etc/default/docker with DOCKER_OPTS="-H tcp://127.0.0.1:2375 -H unix:///var/run/docker.sock" (docker version 1.4.1 in ubuntu 14.04), but it do not take any effect for me. It seems that docker do not read this initital config file because I found export http_proxy enviroment do not work too.

Only sudo docker -H tcp://127.0.0.1:2375 -H unix:///var/run/docker.sock -d works.

It really confused me!

What distro are you using (including version), and where did you get the docker package from, and what version is it?

phemmer · Jan 4, 2015

What distro are you using (including version), and where did you get the docker package from, and what version is it?

I have memtioned it within the question. Docker version 1.4.1, ubuntu 14.04. I'm following the installation guides to install latest version $ sudo apt-get install lxc-docker

seanlook · Jan 4, 2015

I have memtioned it within the question. Docker version 1.4.1, ubuntu 14.04. I'm following the installation guides to install latest version $ sudo apt-get install lxc-docker

$ sudo service docker stop
docker stop/waiting

$ cat /etc/default/docker
# Docker Upstart and SysVinit configuration file

# Customize location of Docker binary (especially for development testing).
#DOCKER="/usr/local/bin/docker"

# Use DOCKER_OPTS to modify the daemon startup options.
DOCKER_OPTS="-H tcp://127.0.0.1:2375"

# If you need Docker to use an HTTP proxy, it can also be specified here.
#export http_proxy="http://127.0.0.1:3128/"

# This is also a handy place to tweak where Docker's temporary files go.
#export TMPDIR="/mnt/bigdrive/docker-tmp"

$ sudo service docker start
$ export DOCKER_HOST=127.0.0.1:2375

$ docker info
Containers: 3
Images: 49
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Dirs: 55
Execution Driver: native-0.2
Kernel Version: 3.13.0-40-generic
Operating System: Ubuntu 14.04.1 LTS
CPUs: 4
Total Memory: 7.679 GiB
Name: thorn
ID: 2MCI:3YT2:XQ4H:AX24:S7BJ:ADF6:L4JT:EKHM:KOIG:CR7N:FOTS:ZCVS

$ docker version
Client version: 1.4.1
Client API version: 1.16
Go version (client): go1.3.3
Git commit (client): 5bc2ff8
OS/Arch (client): linux/amd64
Server version: 1.4.1
Server API version: 1.16
Go version (server): go1.3.3
Git commit (server): 5bc2ff8

I don't seem to be having the same problem. Can you paste the output of your docker info and docker version ?

acbodine · Jan 9, 2015

$ sudo service docker stop
docker stop/waiting

$ cat /etc/default/docker
# Docker Upstart and SysVinit configuration file

# Customize location of Docker binary (especially for development testing).
#DOCKER="/usr/local/bin/docker"

# Use DOCKER_OPTS to modify the daemon startup options.
DOCKER_OPTS="-H tcp://127.0.0.1:2375"

# If you need Docker to use an HTTP proxy, it can also be specified here.
#export http_proxy="http://127.0.0.1:3128/"

# This is also a handy place to tweak where Docker's temporary files go.
#export TMPDIR="/mnt/bigdrive/docker-tmp"

$ sudo service docker start
$ export DOCKER_HOST=127.0.0.1:2375

$ docker info
Containers: 3
Images: 49
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Dirs: 55
Execution Driver: native-0.2
Kernel Version: 3.13.0-40-generic
Operating System: Ubuntu 14.04.1 LTS
CPUs: 4
Total Memory: 7.679 GiB
Name: thorn
ID: 2MCI:3YT2:XQ4H:AX24:S7BJ:ADF6:L4JT:EKHM:KOIG:CR7N:FOTS:ZCVS

$ docker version
Client version: 1.4.1
Client API version: 1.16
Go version (client): go1.3.3
Git commit (client): 5bc2ff8
OS/Arch (client): linux/amd64
Server version: 1.4.1
Server API version: 1.16
Go version (server): go1.3.3
Git commit (server): 5bc2ff8

I don't seem to be having the same problem. Can you paste the output of your docker info and docker version ?

I have installed docker locally yesterday and (probably) ran into this problem. In my case the problem was, that the new docker version (1.4.1) comes with this new /etc/default/docker file (maybe even earlier versions, but the last version I installed and only updated since then on my server, only had the DOCKER_OPTS variable in it and I think it was just empty and not commented out), which has all that stuff in it, but it's all commented out by default.
I tried for like 2 hours to get it working until I noticed that the options were inactive... :(

stozk · Jan 15, 2015

I have installed docker locally yesterday and (probably) ran into this problem. In my case the problem was, that the new docker version (1.4.1) comes with this new /etc/default/docker file (maybe even earlier versions, but the last version I installed and only updated since then on my server, only had the DOCKER_OPTS variable in it and I think it was just empty and not commented out), which has all that stuff in it, but it's all commented out by default.
I tried for like 2 hours to get it working until I noticed that the options were inactive... :(

@stozk +1 for figuring it out though!

acbodine · Jan 15, 2015

@stozk +1 for figuring it out though!

I upgrade docker version 1.3.1 to 1.4.1 and run into this problem. Finally I got my problem resolved by reboot my ubuntu server. Maybe, @stozk is right.

seanlook · Jan 16, 2015

I upgrade docker version 1.3.1 to 1.4.1 and run into this problem. Finally I got my problem resolved by reboot my ubuntu server. Maybe, @stozk is right.

I'm still having this issue.

sudo docker info
Containers: 3
Images: 67
Storage Driver: devicemapper
 Pool Name: docker-8:33-22287262-pool
 Pool Blocksize: 65.54 kB
 Data file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata file: /var/lib/docker/devicemapper/devicemapper/metadata
 Data Space Used: 1.543 GB
 Data Space Total: 107.4 GB
 Metadata Space Used: 3.158 MB
 Metadata Space Total: 2.147 GB
 Library Version: 1.02.82-git (2013-10-04)
Execution Driver: native-0.2
Kernel Version: 3.18.0-031800-generic
Operating System: Ubuntu 14.10


Client version: 1.4.1
Client API version: 1.16
Go version (client): go1.3.3
Git commit (client): 5bc2ff8
OS/Arch (client): linux/amd64
Server version: 1.4.1
Server API version: 1.16
Go version (server): go1.3.3
Git commit (server): 5bc2ff8

AlexAndrascu · Jan 22, 2015

I'm still having this issue.

sudo docker info
Containers: 3
Images: 67
Storage Driver: devicemapper
 Pool Name: docker-8:33-22287262-pool
 Pool Blocksize: 65.54 kB
 Data file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata file: /var/lib/docker/devicemapper/devicemapper/metadata
 Data Space Used: 1.543 GB
 Data Space Total: 107.4 GB
 Metadata Space Used: 3.158 MB
 Metadata Space Total: 2.147 GB
 Library Version: 1.02.82-git (2013-10-04)
Execution Driver: native-0.2
Kernel Version: 3.18.0-031800-generic
Operating System: Ubuntu 14.10


Client version: 1.4.1
Client API version: 1.16
Go version (client): go1.3.3
Git commit (client): 5bc2ff8
OS/Arch (client): linux/amd64
Server version: 1.4.1
Server API version: 1.16
Go version (server): go1.3.3
Git commit (server): 5bc2ff8

got into the same issue.
Ubuntu 14.10 uses systemd instead of sysv-init/upstart
Maybe you should look into /lib/systemd/system/docker.service to change options

fstuess · May 22, 2015

got into the same issue.
Ubuntu 14.10 uses systemd instead of sysv-init/upstart
Maybe you should look into /lib/systemd/system/docker.service to change options

I've also encountered this problem (Debian Jessie 8.0, lxc-docker=1.6.2). After a look around at the configuration files in /lib/systemd/system/, it seems that the Docker configuration file (/lib/systemd/system/docker.service) is not using /etc/default/docker at all. :( The problem is solved by adding an EnvironmentFile directive and modifying the command line to include the options from the file, e.g.

[Unit]
Description=Docker Application Container Engine
Documentation=http://docs.docker.com
After=network.target docker.socket
Requires=docker.socket

[Service]
EnvironmentFile=-/etc/default/docker
ExecStart=/usr/bin/docker -d $DOCKER_OPTS -H fd://
MountFlags=slave
LimitNOFILE=1048576
LimitNPROC=1048576
LimitCORE=infinity

[Install]
WantedBy=multi-user.target

I edited /lib/systemd/system/docker.service to look like the above, ran systemctl daemon-reload, and then restarted the Docker service. This time, it properly launched with the options set in DOCKER_OPTS in my /etc/default/docker.

Again, I'm on Debian Jessie 8.0 with lxc-docker=1.6.2, so YMMV.

zepalmer · Jun 7, 2015

I've also encountered this problem (Debian Jessie 8.0, lxc-docker=1.6.2). After a look around at the configuration files in /lib/systemd/system/, it seems that the Docker configuration file (/lib/systemd/system/docker.service) is not using /etc/default/docker at all. :( The problem is solved by adding an EnvironmentFile directive and modifying the command line to include the options from the file, e.g.

[Unit]
Description=Docker Application Container Engine
Documentation=http://docs.docker.com
After=network.target docker.socket
Requires=docker.socket

[Service]
EnvironmentFile=-/etc/default/docker
ExecStart=/usr/bin/docker -d $DOCKER_OPTS -H fd://
MountFlags=slave
LimitNOFILE=1048576
LimitNPROC=1048576
LimitCORE=infinity

[Install]
WantedBy=multi-user.target

I edited /lib/systemd/system/docker.service to look like the above, ran systemctl daemon-reload, and then restarted the Docker service. This time, it properly launched with the options set in DOCKER_OPTS in my /etc/default/docker.

Again, I'm on Debian Jessie 8.0 with lxc-docker=1.6.2, so YMMV.

Correct, the /etc/default/docker file is only used on systems using "upstart" and "SysVInit", not on systems using systemd.

This is also mentioned at the top of the file;
https://github.com/docker/docker/blob/44fe8cbbd174b5d85d4a063ed270f6b9d2279b70/contrib/init/sysvinit-debian/docker.default#L1

thaJeztah · Jun 7, 2015

Correct, the /etc/default/docker file is only used on systems using "upstart" and "SysVInit", not on systems using systemd.

This is also mentioned at the top of the file;
https://github.com/docker/docker/blob/44fe8cbbd174b5d85d4a063ed270f6b9d2279b70/contrib/init/sysvinit-debian/docker.default#L1

Fair point. On my Debian system, however, the systemd services in /lib/systemd/system/ all include an EnvironmentFile directive to point to the appropriate /etc/defaults/ file. It seems that I should interpret this as an indication that the Ubuntu Docker package isn't, in this somewhat minor way, appropriate for Debian systems. I'll bear this in mind. :)

zepalmer · Jun 7, 2015

Fair point. On my Debian system, however, the systemd services in /lib/systemd/system/ all include an EnvironmentFile directive to point to the appropriate /etc/defaults/ file. It seems that I should interpret this as an indication that the Ubuntu Docker package isn't, in this somewhat minor way, appropriate for Debian systems. I'll bear this in mind. :)

@zepalmer if I'm not mistaken, there's currently some work being done on the installation for those systems, but I'm not 100% clear on what the status is and what changes are made 😊

thaJeztah · Jun 7, 2015

@zepalmer if I'm not mistaken, there's currently some work being done on the installation for those systems, but I'm not 100% clear on what the status is and what changes are made 😊

@zepalmer, as the latest version of the documentation suggests (http://docs.master.dockerproject.org/articles/systemd/), the proper way to edit systemd service file is to create a file in /etc/systemd/system/docker.service.d/<something>.conf and only override the directives you need. The file in /lib/systemd/system/docker.service is "reserved" for the package vendor.

eolamey · Jun 8, 2015

@zepalmer, as the latest version of the documentation suggests (http://docs.master.dockerproject.org/articles/systemd/), the proper way to edit systemd service file is to create a file in /etc/systemd/system/docker.service.d/<something>.conf and only override the directives you need. The file in /lib/systemd/system/docker.service is "reserved" for the package vendor.

Good to know, thanks. My apologies for cluttering up the bug report. :)

zepalmer · Jun 9, 2015

Good to know, thanks. My apologies for cluttering up the bug report. :)

@zepalmer no problem!

thaJeztah · Jun 9, 2015

@zepalmer no problem!

This tripped me up a lot on Ubuntu 15.04 using Docker 1.8.0 experimental via the shell script install process. My assumption is the apt repository package does not provide a proper docker systemd unit file yet?

I ended up having to do a double ExecStart in my override file to clear the original else it would complain about two ExecStart's on a oneshot.

I.e. in /etc/systemd/system/docker.service.d/docker.conf

[Service]
EnvironmentFile=-/etc/default/docker
ExecStart=
ExecStart=docker -d $DOCKER_OPTS ...

rcousens · Jul 13, 2015

This tripped me up a lot on Ubuntu 15.04 using Docker 1.8.0 experimental via the shell script install process. My assumption is the apt repository package does not provide a proper docker systemd unit file yet?

I ended up having to do a double ExecStart in my override file to clear the original else it would complain about two ExecStart's on a oneshot.

I.e. in /etc/systemd/system/docker.service.d/docker.conf

[Service]
EnvironmentFile=-/etc/default/docker
ExecStart=
ExecStart=docker -d $DOCKER_OPTS ...

thanks

for me, my settings were simply located in /etc/systemd/docker file

FYI

[~]$ docker info
Containers: 4
Images: 77
Storage Driver: btrfs
 Build Version: Btrfs v4.1.2+20150724
 Library Version: 101
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.1.6-1-desktop
Operating System: openSUSE 20150823 (Tumbleweed) (x86_64)
CPUs: 8
Total Memory: 15.55 GiB
Name: linux.site
ID: 7JXD:UYXG:ADLO:4DYM:YBSL:GBCO:RGXE:RICT:3WV3:REZX:HIQM:Y773
Username: ____
Registry: https://index.docker.io/v1/
WARNING: No swap limit support

ballPointPenguin · Aug 27, 2015

thanks

for me, my settings were simply located in /etc/systemd/docker file

FYI

[~]$ docker info
Containers: 4
Images: 77
Storage Driver: btrfs
 Build Version: Btrfs v4.1.2+20150724
 Library Version: 101
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.1.6-1-desktop
Operating System: openSUSE 20150823 (Tumbleweed) (x86_64)
CPUs: 8
Total Memory: 15.55 GiB
Name: linux.site
ID: 7JXD:UYXG:ADLO:4DYM:YBSL:GBCO:RGXE:RICT:3WV3:REZX:HIQM:Y773
Username: ____
Registry: https://index.docker.io/v1/
WARNING: No swap limit support

Hi,

I can't find the commits 5c7fa42 and 0e7fb27 any more. Were they published to a branch which is now deleted?

I think, the should be merged into master and/or to the release branch immediately!

mattelacchiato · Oct 16, 2015

Hi,

I can't find the commits 5c7fa42 and 0e7fb27 any more. Were they published to a branch which is now deleted?

I think, the should be merged into master and/or to the release branch immediately!

@mattelacchiato no they were not.
systemd has a built-in method called 'drop-ins' to handle customizing unit files.

https://coreos.com/os/docs/latest/using-systemd-drop-in-units.html

cpuguy83 · Oct 16, 2015

@mattelacchiato no they were not.
systemd has a built-in method called 'drop-ins' to handle customizing unit files.

https://coreos.com/os/docs/latest/using-systemd-drop-in-units.html

Apparently you can override the entire unit file like so:

sudo cp /lib/systemd/system/docker.service /etc/systemd/system/docker.service

and then replacing whatever you need in the new file located within /etc.

netbrain · Oct 20, 2015

Apparently you can override the entire unit file like so:

sudo cp /lib/systemd/system/docker.service /etc/systemd/system/docker.service

and then replacing whatever you need in the new file located within /etc.

@netbrain also see the documentation, which contains some example to override more fine-grained: https://docs.docker.com/articles/systemd/#custom-docker-daemon-options

thaJeztah · Oct 21, 2015

@netbrain also see the documentation, which contains some example to override more fine-grained: https://docs.docker.com/articles/systemd/#custom-docker-daemon-options

@stozk 👍 for providing the fix.

anirudt · Nov 18, 2015

@stozk 👍 for providing the fix.

@thaJeztah That link fixed my issue too. I could clearly see that adding things to /etc/sysconfig/docker was not doing anything but I wasn't really sure the best way to fix it.

Is there anyone I could notify to let them know the docs are wrong on this page:
https://docs.docker.com/engine/articles/configuring/

Or at least put in a link for systemd (Red Hat) installs so others can figure it out faster:
http://docs.docker.com/engine/articles/systemd/#custom-docker-daemon-options

jeffjohnston · Dec 10, 2015

@thaJeztah That link fixed my issue too. I could clearly see that adding things to /etc/sysconfig/docker was not doing anything but I wasn't really sure the best way to fix it.

Is there anyone I could notify to let them know the docs are wrong on this page:
https://docs.docker.com/engine/articles/configuring/

Or at least put in a link for systemd (Red Hat) installs so others can figure it out faster:
http://docs.docker.com/engine/articles/systemd/#custom-docker-daemon-options

@jeffjohnston we do have an open ticket for updating that section; #16770, and the Markdown documents for generating the documentation are in this repository; https://github.com/docker/docker/blob/master/docs/articles/configuring.md so if you're interested in creating a pull request 😇

thaJeztah · Dec 10, 2015

@jeffjohnston we do have an open ticket for updating that section; #16770, and the Markdown documents for generating the documentation are in this repository; https://github.com/docker/docker/blob/master/docs/articles/configuring.md so if you're interested in creating a pull request 😇

@thaJeztah Thank you for the link. I think I will attempt that this weekend.

jeffjohnston · Dec 10, 2015

@thaJeztah Thank you for the link. I think I will attempt that this weekend.

That'd be awesome @jeffjohnston!

thaJeztah · Dec 10, 2015

That'd be awesome @jeffjohnston!

@jeffjohnston @thaJeztah - anyone updating the docs ? I just spent a lot of wasted time trying to figure out what's wrong with my docker setup just because of the systemd config file issue

sandys · Jan 2, 2016

@jeffjohnston @thaJeztah - anyone updating the docs ? I just spent a lot of wasted time trying to figure out what's wrong with my docker setup just because of the systemd config file issue

@sandys I see the section for CentOS/RHEL was updated in #18620, but the Ubuntu section not yet. I'll reopen #16770. If you're interested in opening a PR to fix that, let us know.

thaJeztah · Jan 2, 2016

@sandys I see the section for CentOS/RHEL was updated in #18620, but the Ubuntu section not yet. I'll reopen #16770. If you're interested in opening a PR to fix that, let us know.

If you use options that need expansion, e.g.: DOCKER_OPTS="-g $(readlink -f /var/lib/docker)" then this might help:

[ ! -e /etc/systemd/system/docker.service.d/ ] && mkdir -p /etc/systemd/system/docker.service.d/
cat << 'EOF' > /etc/systemd/system/docker.service.d/docker.conf
# Load /etc/default/docker from SystemD init script
# References: 
#  https://github.com/docker/docker/issues/9889#issuecomment-120927382
#  https://gist.github.com/nickjacob/9909574

[Service]
# This line is sufficient if DOCKER_OPTS variable does not have to be expanded:
#EnvironmentFile=-/etc/default/docker
# Use this line to expand DOCKER_OPTS variable:
ExecStartPre=/bin/sh -c ". /etc/default/docker && /bin/systemctl set-environment DOCKER_OPTS=\"$DOCKER_OPTS\""

ExecStart=
ExecStart=/usr/bin/dockerd -H fd:// $DOCKER_OPTS

EOF

systemctl daemon-reload 
service docker restart

JM1 · Aug 24, 2016

If you use options that need expansion, e.g.: DOCKER_OPTS="-g $(readlink -f /var/lib/docker)" then this might help:

[ ! -e /etc/systemd/system/docker.service.d/ ] && mkdir -p /etc/systemd/system/docker.service.d/
cat << 'EOF' > /etc/systemd/system/docker.service.d/docker.conf
# Load /etc/default/docker from SystemD init script
# References: 
#  https://github.com/docker/docker/issues/9889#issuecomment-120927382
#  https://gist.github.com/nickjacob/9909574

[Service]
# This line is sufficient if DOCKER_OPTS variable does not have to be expanded:
#EnvironmentFile=-/etc/default/docker
# Use this line to expand DOCKER_OPTS variable:
ExecStartPre=/bin/sh -c ". /etc/default/docker && /bin/systemctl set-environment DOCKER_OPTS=\"$DOCKER_OPTS\""

ExecStart=
ExecStart=/usr/bin/dockerd -H fd:// $DOCKER_OPTS

EOF

systemctl daemon-reload 
service docker restart

On Ubuntu. If you experience error:

x509: cannot validate certificate for [IP address or domain name] because it doesn't contain any IP SANs

On the Docker registry the certificate had to be compiled with the subjectAltName as described here:
https://docs.docker.com/engine/security/https/

Here is the code for convenience:
$ echo subjectAltName = IP:10.10.10.20,IP:127.0.0.1 > extfile.cnf
$ openssl x509 -req -days 365 -sha256 -in server.csr -CA ca.pem -CAkey ca-key.pem
-CAcreateserial -out server-cert.pem -extfile extfile.cnf

Note, I was able to check the subject alternative name is present in the certificate using the following command:
openssl x509 -in certificate.crt -text -noout

However, on Ubuntu 14 client (i.e. Docker Engine)
This error was followed suit by
x509: certificate signed by unknown authority

For people using Ubuntu 14.
The config file that is used for the Docker engine (that I want to use to connect to the Docker Registry):
/etc/default/docker

in there, you need to specify the docker options:
DOCKER_OPTS="--insecure-registry myinsecure.com:5000"

Then restart the daemon (add sudo if you user is not allowed to start a docker service):
$ [sudo] service docker restart

The value does not need to be a domain name, it simply has to match what you certificate is registered with; I have an IP address with a port and this works... (i.e. e.g. 100.100.100.100:100)

All this took me a day, so, I am posting this hoping that it will be useful to other people...

JazzDeben · Sep 16, 2016

On Ubuntu. If you experience error:

x509: cannot validate certificate for [IP address or domain name] because it doesn't contain any IP SANs