Docker Server Configuration: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 68: Line 68:
The file can be edited and committed, and the daemon restart.
The file can be edited and committed, and the daemon restart.


=Files=
=daemon.json=
 
==/etc/sysconfig/docker==
 
{{Internal|/etc/sysconfig/docker|/etc/sysconfig/docker}}
 
==/etc/docker/daemon.json==


{{Internal|/etc/docker/daemon.json|/etc/docker/daemon.json}}
{{Internal|/etc/docker/daemon.json|/etc/docker/daemon.json}}

Revision as of 20:31, 20 April 2018

External

Internal

Overview

Server Configuration Options

--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

Also see:

Docker Concepts - Container Networking

--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

Docker Image Registry

--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

--log-driver

--signature-verification

OS-Dependent Details

RedHat/Centos

Daemon configuration parameters are usually provided in /etc/sysconfig/docker:

Ubuntu

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.

daemon.json

/etc/docker/daemon.json

Docker Container Configuration

Docker Container Configuration