You are not logged in.

#1 2025-02-25 13:07:31

tokenize
Member
Registered: 2022-07-27
Posts: 17

Docker breaking changes

Since the latest docker package update there's a breaking change if you don't have ipv6 enabled in your system which will result in the following message in the logs:

fev 25 13:00:39 REDACTED dockerd[3206]: failed to start daemon: Error initializing network controller: error creating default "bridge" network: add inter-network communication rule:  (iptables failed: ip6tables --wait -t filter -A DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2: ip6tab>
fev 25 13:00:39 REDACTED dockerd[3206]: Perhaps ip6tables or your kernel needs to be upgraded.
fev 25 13:00:39 REDACTED dockerd[3206]:  (exit status 3))

To fix this, you need to add the following option to your /etc/docker/daemon.json (create the file if it doesn't exist):
{"ip6tables": false}

More info here: https://docs.docker.com/engine/release-notes/27/#ipv6

Last edited by tokenize (2025-02-25 13:08:04)

Offline

#2 2025-02-27 13:24:28

Zerby
Member
Registered: 2025-02-27
Posts: 1

Re: Docker breaking changes

This didn't work for me.
I had to enable ip6tables and now everything works.

sudo systemctl enable ip6tables

It now works even without disabling the ipv6 using the json

Offline

#3 2025-02-27 14:03:51

tokenize
Member
Registered: 2022-07-27
Posts: 17

Re: Docker breaking changes

The option is "ip6tables", not ipv6.

Offline

#4 2025-02-28 13:33:33

carport
Member
Registered: 2025-02-28
Posts: 7

Re: Docker breaking changes

Thank you.

For those wondering, if your file was empty or didn't exist, it will be:

{
  "ip6tables": false
}

If there was already content on it, like "features", then it'll be like:

{
  "features": {
    "containerd-snapshotter": true
  },

  "ip6tables": false
}

Offline

Board footer

Powered by FluxBB