You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
libnetwork has been merged to the main repo of Moby since Docker 22.06.
The old libnetwork repo (https://github.com/moby/libnetwork) now only accepts PR for Docker 20.10,
and will be archived after the EOL of Docker 20.10.
Sorry to trouble all of you.
Recently, I follow the guidance to enable ipv6 for the docker in my linux machine
I directly edit the /etc/docker/daemon.json file for adding these parameters:
"ipv6": true,
"ip6tables": true,
"experimental": true,
"fixed-cidr-v6": "2001:db8:abc1::/64"
Then just restart the docker.
Then for example, here are two ipv6 addresses
static ipv6 address A
DHCP(dynamic) generated ipv6 address B
Case1:
When I use "ping6 A" in my linux machine, it works with response
Case2:
When I use "ping6 B" in my linux machine, it works but should have a zone identifier behind, like "B%eth0"
Case3:
when I use "docker exec -it myDocker bash" to get inside a docker, and then run "ping6 A", it works with response
Case4:
when I use "docker exec -it myDocker bash" to get inside a docker, and then run "ping6 B", it always throws the error message "ping6: sendto: Invalid argument"
Then I also try "ping6 B%eth0", it will be time out without any response.
For case4, I do not understand, for DHCP generated ipv6 address, why we cannot use it or ping6 it inside the docker? Why the docker cannot automatically assign a zone identifier to it? what is the problem here? how to fix it?
Thanks a lot. Really need your help.
The text was updated successfully, but these errors were encountered:
Hi, could you please send the output of
ip -f inet6 addr show
From within the container and from the host?
Also, there is/was a problem with a /64, can you try again with a /80 ?
Kind regards,
Ed
On 3/24/23 09:52, Haochen Sui wrote:
*Warning*
libnetwork was moved to
https://github.com/moby/moby/tree/master/libnetwork
libnetwork has been merged to the main repo of Moby since Docker
22.06.
The old libnetwork repo (https://github.com/moby/libnetwork) now
only accepts PR for Docker 20.10,
and will be archived after the EOL of Docker 20.10.
Sorry to trouble all of you.
Recently, I follow the guidance to enable ipv6 for the docker in my
linux machine
I directly edit the /etc/docker/daemon.json file for adding these
parameters:
"ipv6": true,
"ip6tables": true,
"experimental": true,
"fixed-cidr-v6": "2001:db8:abc1::/64"
Then just restart the docker.
Then for example, here are two ipv6 addresses
static ipv6 address A
DHCP(dynamic) generated ipv6 address B
Case1:
When I use "ping6 A" in my linux machine, it works with response
Case2:
When I use "ping6 B" in my linux machine, it works but should have a
zone identifier behind, like "B%eth0"
Case3:
when I use "docker exec -it myDocker bash" to get inside a docker, and
then run "ping6 A", it works with response
Case4:
when I use "docker exec -it myDocker bash" to get inside a docker, and
then run "ping6 B", it always throws the error message "ping6: sendto:
Invalid argument"
Then I also try "ping6 B%eth0", it will be time out without any response.
For case4, I do not understand, for DHCP generated ipv6 address, why
we cannot use it or ping6 it inside the docker? Why the docker cannot
automatically assign a zone identifier to it? what is the problem
here? how to fix it?
Thanks a lot. Really need your help.
—
Reply to this email directly, view it on GitHub
<#2675>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPTWE4UTWU3YOEKML72E73W5VOGHANCNFSM6AAAAAAWGIS3KQ>.
You are receiving this because you are subscribed to this
thread.Message ID: ***@***.***>
Sorry to trouble all of you.
Recently, I follow the guidance to enable ipv6 for the docker in my linux machine
I directly edit the /etc/docker/daemon.json file for adding these parameters:
"ipv6": true,
"ip6tables": true,
"experimental": true,
"fixed-cidr-v6": "2001:db8:abc1::/64"
Then just restart the docker.
Then for example, here are two ipv6 addresses
static ipv6 address A
DHCP(dynamic) generated ipv6 address B
Case1:
When I use "ping6 A" in my linux machine, it works with response
Case2:
When I use "ping6 B" in my linux machine, it works but should have a zone identifier behind, like "B%eth0"
Case3:
when I use "docker exec -it myDocker bash" to get inside a docker, and then run "ping6 A", it works with response
Case4:
when I use "docker exec -it myDocker bash" to get inside a docker, and then run "ping6 B", it always throws the error message "ping6: sendto: Invalid argument"
Then I also try "ping6 B%eth0", it will be time out without any response.
For case4, I do not understand, for DHCP generated ipv6 address, why we cannot use it or ping6 it inside the docker? Why the docker cannot automatically assign a zone identifier to it? what is the problem here? how to fix it?
Thanks a lot. Really need your help.
The text was updated successfully, but these errors were encountered: