Running Docker / Alpine Linux in an IPv6-only environment

By on 23 May 2022

Category: Tech matters

Tags: , , ,


Blog home

This month, my virtual private server started offering IPv6-only as a general service. 

At the OS level, both servers and clients support IPv4 and IPv6 network environments using dual-stack but there are quite a few HTTP/HTTPS servers that do not yet have AAAA records. By default, the Docker server configures container networks for IPv4-only, so I had a hard time running it in this environment.

To help others facing similar scenarios, I wanted to share my experience running Docker/Alpine Linux in the IPv6-only environment of Rocky Linux 8.5.

Installing Docker

First, install Docker using the dnf command.

sudo dnf update -y
sudo dnf install -y dnf-utils device-mapper-persistent-data lvm2
sudo dnf config-manager --add-repo
sudo dnf makecache
sudo dnf install -y docker-ce
sudo systemctl start docker
sudo systemctl enable docker

I used the dnf command because yum is not recommended on recent CentOS Linux.

Permission settings for users running Docker

If you want to run Docker somewhere other than root, set your user to belong to the Docker group.

sudo groupadd docker
#groupadd: group'docker' already exists
sudo usermod -aG docker $ USER

Create a daemon .json for IPv6

Add IPv6-compatible settings to the Docker daemon startup options at /etc/docker/daemon.json.

sudo vi /etc/docker/daemon.json

The contents of the created file are as follows:

  "ipv6": true,
  "fixed-cidr-v6": "fd11:2233:4455:6677::/64",
  "registry-mirrors": [""]

Docker’s default registry only returns IPv4 addresses, so you can’t communicate in an IPv6-only environment. In this case, set Google’s registry mirror that supports IPv6. The fixed-cidr-v6 setting is a Unique Local Address (ULA) that you set yourself and is equivalent to an IPv6 private address. To use it, specify any address starting with ‘fd.’, for example fd11:2233:4455:6677::/64

Restart Docker

Restart Docker for these settings to take effect.

sudo systemctl restart docker

If you get an error, review the daemon.json configuration file and fix it.

Add NAT with ip6tables

Set NAT in fixed-cidr-v6 of daemon.json so that you can communicate outwards from the internal network.

sudo ip6tables -t nat -A POSTROUTING -s fd11:2233:4455:6677::/64 ! -o docker0 -j MASQUERADE

Check if the NAT table has been added correctly by specifying -t nat as an argument.

sudo ip6tables -t nat -L
MASQUERADE all fd11:2233:4455:6677::/64 anywhere 

It’s okay if the following has the line MASQUERADE all fd11:2233:4455:6677::/64 anywhere in the output.

target prot opt ​​source destination

Chain INPUT (policy ACCEPT)
target prot opt ​​source destination

target prot opt ​​source destination
MASQUERADE all fd11:2233:4455:6677::/64 anywhere

Chain OUTPUT (policy ACCEPT)
target prot opt ​​source destination

Rc.local settings on reboot

Set rc.local so that the NAT setting is valid even after rebooting.

sudo vi /etc/rc.d/rc.local

The rc.local is a backwards compatibility file but you should add the following line at the end.

#It is highly advisable to create own systemd services or udev rules
#to run scripts during boot instead of using this file.
# In contrast to previous versions due to parallel execution during boot
#this script will NOT be run after all other services.
# Please note that you must run'chmod +x /etc/rc.d/rc.local' to ensure
#that this script will be executed during boot.


ip6tables -t nat -A POSTROUTING -s fd11:2233:4455:6677::/64 ! -o docker0 -j MASQUERADE

If this is your first time setting up rc.local, run the following command to make it run on reboot:

sudo chmod +x /etc/rc.d/rc.local
sudo systemctl start rc-local

Check the current settings with Docker info

Run docker info to see the current settings. You should get an output like this:

Client: Client:
 Context: default
 Debug Mode: false
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Docker Buildx (Docker Inc., v0.8.1-docker)
  scan: Docker Scan (Docker Inc., v0.17.0)

~ Omitted ~
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
 Registry Mirrors:
 Live Restore Enabled: false

It’s not a problem if the output has in Registry Mirrors:.

Creating a Dockerfile for Alpine Linux

Create a Dockerfile in a directory of your choice with vi Dockerfile. The contents of the Dockerfile are as follows:

FROM alpine: 3.15.4
RUN apk update && apk add bind-tools curl
CMD ["/bin/sh"]

After pulling the image of alpine:3.15.4, I wanted to use the dig command and curl command, so I installed the bind tools and curl apk package and start the shell by default.

Build Docker

The tag name can be whatever you like, but you must build Docker with ipv6/alpine.

docker build -t ipv6/alpine

If you can download the apk package from the IPv6 server and get the following result at build time, it has been successful.

Sending build context to Docker daemon 3.072kB
Step 1/3: FROM alpine: 3.15.4
3.15.4: Pulling from library/alpine
df9b9388f04a: Pull complete
Digest: sha256: 4edbd2beb5f78b1014028f4fbb99f3237d9561100b6881aabbf5acce2c4f9454
Status: Downloaded newer image for alpine: 3.15.4
 ---> 0ac33e5f5afa
Step 2/3: RUN apk update && apk add bind-tools curl
 ---> Running in a1ebb762c17e
v3.15.4-78-ge239b26b75 []
v3.15.4-79-gaf675e239c []
OK: 15855 distinct packages available
(1/18) Installing fstrm (0.6.1-r0)
(2/18) Installing krb5-conf (1.0-r2)
(3/18) Installing libcom_err (1.46.4-r0)
(4/18) Installing keyutils-libs (1.6.3-r0)
(5/18) Installing libverto (0.3.2-r0)
(6/18) Installing krb5-libs (1.19.3-r0)
(7/18) Installing json-c (0.15-r1)
(8/18) Installing protobuf-c (1.4.0-r0)
(9/18) Installing libuv (1.42.0-r0)
(10/18) Installing xz-libs (5.2.5-r1)
(11/18) Installing libxml2 (2.9.13-r0)
(12/18) Installing bind-libs (9.16.27-r0)
(13/18) Installing bind-tools (9.16.27-r0)
(14/18) Installing ca-certificates (20211220-r0)
(15/18) Installing brotli-libs (1.0.9-r5)
(16/18) Installing nghttp2-libs (1.46.0-r0)
(17/18) Installing libcurl (7.80.0-r1)
(18/18) Installing curl (7.80.0-r1)
Executing busybox-1.34.1-r5.trigger
Executing ca-certificates-20211220-r0.trigger
OK: 15 MiB in 32 packages
Removing intermediate container a1ebb762c17e
 ---> 18d7e9a3b51b
Step 3/3: CMD ["/bin/sh"]
 ---> Running in ccda19d240b3
Removing intermediate container ccda19d240b3
 ---> ff8bbe4b67c8
Successfully built ff8bbe4b67c8
Successfully tagged ipv6/alpine: latest

If there are no errors, it has been successful. Congratulations!

Errors in

If you get the following error when building Docker, it has failed.

Sending build context to Docker daemon 4.096kB
Step 1/3: FROM alpine: 3.15.4
Get "": dial tcp connect: network is unreachable

This means does not have an IPv6 AAAA record and you are trying to communicate with an IPv4 address.

In this case, you’ll need to specify "registry-mirrors": [""] in the above daemon.json so the mirror server can communicate with IPv6. If that fails, it may be that the download URL is mis-cached by Docker. Try changing the setting and downloading another version such as FROM alpine: 3.15.4 or FROM alpine: 3.15.2.

If you get an error on dl-cdn

If you get the following error when building Docker, it is failing because you cannot communicate from outwards from Docker in an IPv6-only environment.

ERROR: temporary error (try again later)
WARNING: Ignoring No such file or directory
ERROR: temporary error (try again later)
WARNING: Ignoring No such file or directory

The ip6tables NAT is necessary to communicate from the internal network and is specified with "fixed-cidr-v6": "fd11:2233:4455:6677::/64" in the daemon.json mentioned above. You need to check if it is enabled.

Also, as of 3 May 2022, is dual-stacked and has IPv6 AAAA records, so you should be able to communicate in an IPv6-only environment.

$ dig A
; <<>> DiG 9.11.26-RedHat-9.11.26-6.el8 <<>> A
~ Omitted ~
; IN A

$ dig AAAA

; <<>> DiG 9.11.26-RedHat-9.11.26-6.el8 <<>> AAAA
~ Omitted ~

;; ANSWER SECTION: 1484 IN CNAME 30 IN AAAA 2a04:4e42:1a::645

If the server does not return AAAA records, it will fail when trying to communicate with an IPv4 address. To fix this, specify a mirror server that can communicate with IPv6, such as by executing with Dockerfile:

RUN sed -r "s;//;//;g" -i /etc/apk/repositories

You can check the list of official mirror servers at Official Alpine Linux mirrors.

Run Docker

Docker runs with the tag name ipv6/alpine specified at build time. You can run the shell interactively with the -i option.

docker container run -it ipv6/alpine

After successfully entering the shell, use the curl command to check if HTTP communication with the IPv6 server is possible.

/ # cd / tmp
/ tmp # curl
<HTML> <HEAD> <meta http-equiv = "content-type" content = "text / html; charset = utf-8">
<H1>301 Moved</H1>
The document has moved
<A HREF="">here</A>.
/tmp #

A 301 response indicates success, showing it was possible to communicate with IPv6-only. Congratulations.

BusyBox wget isn’t completely compatible with IPv6

BusyBox’s wget is not fully IPv6 compliant, so it’s a good idea to replace the wget command with apk add wget or use the curl command.

Translation: When resolving a name with busybox wget in an IPv6-only environment, the IPv4 address is prioritized and cannot be downloaded. Problem: (sa_family_t) AF_UNSPEC is specified for str2sockaddr in the wrapper function xhost2sockaddr, and multiple IP addresses are specified by getaddrinfo. A trap that uses the first IP as it is when (v4 / v6) is returned.

It would be great if the Internet could be used more in an IPv6-only environment.

Translated and adapted from the original post on Hatena Blog.

Yoshinori Takesako is the founder of SECCON.

Rate this article

The views expressed by the authors of this blog are their own and do not necessarily reflect the views of APNIC. Please note a Code of Conduct applies to this blog.


  1. Nick Tait

    Its a shame that you went to the trouble to document how to get Docker to work with IPv6, but then resorted to using ULA and NAT? Maybe you had no choice but to use NAT, due to constraints imposed on your Virtual Private Server, but it would have been good if this topic was discussed before you went ahead with the “here is how to do it” part?

    There are very few justified applications for NAT with IPv6, and I’d encourage anyone interested in knowing more about this to read:

    IMHO This article would have been so much more useful if it had discussed how to get Docker to work with a globally routeable IPv6 address obtained using DHCPv6 Prefix Delegation?

  2. Jakub

    I stopped reading after the “Unique Local Address (ULA) that you set yourself and is equivalent to an IPv6 private address”.

  3. Fayçal

    Very good idea to promote IPv6-only four using docker but why promoting IPv6 if this is for using ULA + Nat66 …why not promoting IPv6 only with GUA ( Public IPv6 addresses) IPv6 addresses ?


Leave a Reply

Your email address will not be published. Required fields are marked *