Docker Server Configuration: Difference between revisions
| (14 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
=Overview= | =Overview= | ||
= | =Server Startup Sequence= | ||
==RedHat/Centos systemd== | ==RedHat/Centos systemd== | ||
[[Systemd_Concepts#Overview|systemd]] Docker Unit File: /usr/lib/systemd/system/docker.service | [[Systemd_Concepts#Overview|systemd]] Docker Unit File: /usr/lib/systemd/system/docker.service. Depending on the distribution, the unit file may or may not refer configuration from /etc/sysconfig/docker. | ||
= | =Server Startup Configuration= | ||
{{Note|[[daemon.json]] also contains server configuration and it is an alternative to configuration specified as command line parameters and in various startup configuration files read when the server is started.}} | |||
==OS-Dependent Startup Configuration Files Details== | |||
===RedHat/Centos=== | |||
Daemon configuration parameters are usually provided in /etc/sysconfig/docker. However, the availability of this file may depend on distribution and installation procedure. | |||
===Mac=== | |||
The simples possible way to configure the Docker daemon on Mac is to use the UI: the whale icon-> Preferences -> Daemon. | |||
The "Basic" section has UI elements to configure [[Docker_Server_Configuration#--insecure-registry|insecure registries]] and registry mirrors. A configuration change applied here propagates to the "[[#Mac_Preferences_Advanced|Advanced]]" section after daemon restart. | |||
<span id='Mac_Preferences_Advanced'></span>The "Advanced" section gives access to the content of [[daemon.json]] file, which can be edited freely. However, the danger is that a configuration error saved here will prevent the daemon to start. If that happens, the file-system version of the same file can be accessed as follows: | |||
cd ~/Library/Containers/com.docker.docker/Data/database | |||
git reset --hard HEAD | |||
The daemon.json becomes available as: | |||
~/Library/Containers/com.docker.docker/Data/database/com.docker.driver.amd64-linux/etc/docker/daemon.json | |||
The file can be edited and committed, and the daemon restart. | |||
=<span id='Server_Command_Line_Options'></span>Server Configuration Options= | =<span id='Server_Command_Line_Options'></span>Server Configuration Options= | ||
The following options are Docker server command line options and should be provided on the dockerd daemon command line, [[#Server_Startup_Sequence|when started]]. | |||
==--insecure-registry== | ==--insecure-registry== | ||
| Line 31: | Line 58: | ||
==--net== | ==--net== | ||
Also see | <font color='darkgray'>Not found in Docker 18.03-ce. Also see [[Docker_Networking_Concepts#Network_Drivers|Docker Networking Concepts]]</font>. | ||
==--selinux-enabled== | ==--selinux-enabled== | ||
| Line 39: | Line 66: | ||
When asked to search for or pull images, the docker runtime uses the Docker registry (docker.io) to complete those activities. Additional registries can be added to the list with --add-registry. | When asked to search for or pull images, the docker runtime uses the Docker registry (docker.io) to complete those activities. Additional registries can be added to the list with --add-registry. | ||
Also see {{Internal|Docker_Concepts#Image_Registry|Docker Image Registry}} | Also see: {{Internal|Docker_Concepts#Image_Registry|Docker Image Registry}} | ||
==--block-registry== | ==--block-registry== | ||
| Line 50: | Line 77: | ||
==--signature-verification== | ==--signature-verification== | ||
=daemon.json= | =daemon.json= | ||
Latest revision as of 20:51, 2 October 2018
External
Internal
Overview
Server Startup Sequence
RedHat/Centos systemd
systemd Docker Unit File: /usr/lib/systemd/system/docker.service. Depending on the distribution, the unit file may or may not refer configuration from /etc/sysconfig/docker.
Server Startup Configuration
daemon.json also contains server configuration and it is an alternative to configuration specified as command line parameters and in various startup configuration files read when the server is started.
OS-Dependent Startup Configuration Files Details
RedHat/Centos
Daemon configuration parameters are usually provided in /etc/sysconfig/docker. However, the availability of this file may depend on distribution and installation procedure.
Mac
The simples possible way to configure the Docker daemon on Mac is to use the UI: the whale icon-> Preferences -> Daemon.
The "Basic" section has UI elements to configure insecure registries and registry mirrors. A configuration change applied here propagates to the "Advanced" section after daemon restart.
The "Advanced" section gives access to the content of daemon.json file, which can be edited freely. However, the danger is that a configuration error saved here will prevent the daemon to start. If that happens, the file-system version of the same file can be accessed as follows:
cd ~/Library/Containers/com.docker.docker/Data/database git reset --hard HEAD
The daemon.json becomes available as:
~/Library/Containers/com.docker.docker/Data/database/com.docker.driver.amd64-linux/etc/docker/daemon.json
The file can be edited and committed, and the daemon restart.
Server Configuration Options
The following options are Docker server command line options and should be provided on the dockerd daemon command line, when started.
--insecure-registry
This option instructs the Docker daemon to trust any Docker registry on the indicated subnet, rather than requiring a certificate. The default value is []. For OpenShift-integrated Docker, the subnet where Docker expects this registry is the OpenShift SDN services subnet.
... --insecure-registry <list> ...
--insecure-registry 172.30.0.0/16
The same option can be configured in daemon.json with insecure-registries.
--net
Not found in Docker 18.03-ce. Also see Docker Networking Concepts.
--selinux-enabled
--add-registry
When asked to search for or pull images, the docker runtime uses the Docker registry (docker.io) to complete those activities. Additional registries can be added to the list with --add-registry.
Also see:
--block-registry
To prevent users from pulling images from the Docker registry, after presumably other registry has been configured with --add-registry, use
--block-registry docker.io