Frequently Asked Question

Docker Networking at EODC
Last Updated 4 years ago

1. Introduction

Please note - These issues do not affect "host" networking mode.
Therefore it is recommended to use host networking during build stages where other network configurations may not apply.
Depending on your use case, this may also be suitable for the container itself.


Network connectivity issues with a vanilla Docker installation.

This is due to Docker not analyzing the MTU size of the network interfaces on hosts.
Your networks within the EODC Cloud operate with an MTU of 1450, Docker networks require additional configuration.


This guide shows how to set Docker's networking to function correctly within these networks.

2. Docker

2.1 Docker OpenStack VM config

Add following line: to the JSON object located at
/etc/docker/daemon.json

N.B This file can be created if it does not already exist.

{
    "mtu": 1450
}

To apply this change it may be necessary to restart the docker daemon. To do this run:

sudo systemctl restart docker

2.1 Docker compose

Docker Compose runs it's own network - so the fix for the Docker daemon does not fix the same issues with Docker Compose. In this case it is necessary to add the following lines in your docker-compose.yml file.

version: '3'
services:
# Add services here...
networks:
  default:
    driver: bridge
    driver_opts:
      com.docker.network.driver.mtu: 1450
This website relies on temporary cookies to function, but no personal data is ever stored in the cookies. For further information see our

privacy policy.

Accept

Loading ...