DBerry2 Posted March 2, 2019 Share Posted March 2, 2019 Hey everyone, I have IPv6 setup on my network and would like to setup some dockers to use a Fixed IPv6 address but so far I haven't been able to set a container with an IPv6 address. it seems even though the fixed IP address has my IPv6 subnet on it I can't use it. if I put an IPv6 address in there I get an error when I try to update the container. the error I get is invalid ipv4 address but I'm trying to use a IPv6 address Has anyone been able to get this working? Quote Link to comment
knex666 Posted March 2, 2019 Share Posted March 2, 2019 You try to setup an ipv6 with the ipv4 tag, thats not right. Normally docker will automaticly setup ipv6 for your container. You can find that out by listing your docker network. If you want to set up your own fix address use the extra parameter (There is one extra input in the docker form) - - ipv6='1234:5678:abcd:efab' (--ipv6 without empty spaces) Cheers Quote Link to comment
bonienl Posted March 3, 2019 Share Posted March 3, 2019 (edited) On 3/2/2019 at 1:19 AM, DBerry2 said: it seems even though the fixed IP address has my IPv6 subnet on it I can't use it. if I put an IPv6 address in there I get an error when I try to update the container. This is a bug and corrected in the next release. It will be possible to assign both an IPv4 and IPv6 address. E.g. As a temporary workaround use the extra parameters field and set the IPv6 address. --ip6='2a02:aaaa:bbbb:101::100' Edited March 3, 2019 by bonienl Quote Link to comment
DesertCookie Posted April 1, 2022 Share Posted April 1, 2022 (edited) On 3/3/2019 at 8:46 AM, bonienl said: It will be possible to assign both an IPv4 and IPv6 address. E.g. I tried this but it does not seem to work. The container is not pingable via its IPv6 address. I noticed there apparently are two different IPv6 ranges. The one displayed when editing the container and the range from the Docker settings differ (censored parts that match): XXXX:XXXX:5520:e500::/64 -- Container Settings XXXX:XXXX:555e:a600::/64 -- Docker Settings When I use "XXXX:XXXX:5520:e500::105" the container starts but is not pingable. When I use the base from the Docker settings the container doesn't start with an "error code 403". I am using a custom bridge to make the container appear as its own device on my local network. Edited April 1, 2022 by DesertCookie Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.