Introduction

A story that happened when using the address band 172.17.xxx.xxx on a physical network.

Ubuntu 18.04.3 LTS Docker version 19.03.5

Main subject

The bridge interface automatically generated by Docker uses 172.17.0.xxx/16 and ** Interfered with the physical network address band **.

It seems that you can specify the IP address when it is automatically generated in /etc/docker/daemon.json.

`/etc/docker/daemon.json`


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

As a point

-- bip is for docker0 -- default-address-pools is for br-xxxxxxxxxxxx --Even if there is no bip, it is automatically generated from default-address-pools, so you can omit it.

was.

Recommended Posts

IP address interfered with Docker bridge

Translate IP address

CentOS IP address Setup

Rails deploy with Docker

Run Pico with docker

Explode Docker with WSL2

Use Puphpeteer with Docker

Operate Emby with Docker

Try WildFly with Docker

Use ngrok with Docker

Run Payara with Docker

[Docker] Connection with MySQL

Php settings with Docker

Getting Started with Docker

Disposable PHP with Docker

Install Composer with Docker

Find the address class and address type from the IP address with Java

Use GDAL with Python with Docker

Deploy with EC2 / Docker / Laravel

Run TAO Core with Docker

Docker management with VS Code

Set up GitLab with docker

Run Rails whenever with docker

Get started with DynamoDB with docker

Docker autostart settings with wsl2

[Docker] Rails 5.2 environment construction with docker

Spring Boot starting with Docker

Build docker environment with WSL

Version control CocoaPods with Docker

Web application built with docker (1)

I tried BIND with Docker

React environment construction with Docker

Build DynamoDB local with Docker

[Docker] Use whenever with Docker + Rails

Using PlantUml with Honkit [Docker]