Daemon.json: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 5: Line 5:
=Overview=  
=Overview=  


/etc/docker/daemon.json contains server configuration and it is an alternative to configuration specified as command line parameters when the server is started. Initially, daemon.json is empty or missing altogether. The file lives in different places on different systems. On RedHat/Centos, it is stored in. On Mac installations, the file can be found following the procure specified here: [[Docker_Server_Configuration#Mac|Docker Server Configuration on Mac]].
/etc/docker/daemon.json contains server configuration and it is an alternative to configuration specified as command line parameters when the server is started. Initially, daemon.json is empty or missing altogether. The file lives in different places on different systems. On RedHat/Centos and Ubuntu, it is stored in /etc/docker/daemon.json. On Mac installations, the file can be found following the procure specified here: [[Docker_Server_Configuration#Mac|Docker Server Configuration on Mac]].


=Configuration=
=Configuration=

Revision as of 17:26, 30 April 2018

Internal

Overview

/etc/docker/daemon.json contains server configuration and it is an alternative to configuration specified as command line parameters when the server is started. Initially, daemon.json is empty or missing altogether. The file lives in different places on different systems. On RedHat/Centos and Ubuntu, it is stored in /etc/docker/daemon.json. On Mac installations, the file can be found following the procure specified here: Docker Server Configuration on Mac.

Configuration

insecure-registries

{
  "insecure-registries" : ["192.168.1.10:5000"]
}

The same behavior can be specified by setting command-line startup parameter --insecure-registry.

The Default Bridge Network

daemon.json contains a section that can be used to configure the default bridge network. Note that the default bridge network is considered legacy and user-defined bridge networks should be used instead.

{
  "bip": "192.168.1.5/24",
  "fixed-cidr": "192.168.1.5/25",
  "fixed-cidr-v6": "2001:db8::/64",
  "mtu": 1500,
  "default-gateway": "10.20.1.1",
  "default-gateway-v6": "2001:db8:abcd::89",
  "dns": ["10.20.1.2","10.20.1.3"]
}