Appendix. Common problems and solutions

This section describes the errors most often encountered during the installation of the Service and actions to fix them.

Server IP-address and Docker conflict

If the server on which Docker is deployed has an IP address like 172.17.0.0/16, this leads to a conflict between the physical network and the default Docker network. To change the Docker network, follow these steps.

Edit or create a new Docker config file daemon.json:

nano /etc/docker/daemon.json

Add to the config file the lines:

{
  "default-address-pools":
  [
    {"base":"10.10.0.0/16","size":24}
  ]
}

Restart Docker:

service docker restart

Check the changes:

docker network create foo
docker
| network inspect foo | grep Subnet

The result should be:

Subnet: 10.10.1.0/24

This algorithm works the same for Docker Compose.

Go to the container:

docker-compose run --rm point_auth sh

Check component availability:

curl point_auth:9000/version

Exit the container:

Ctrl+D

If the Service and dependent components are located on the same server, it may be necessary to open ports or launch them on the host network.