diff options
| author | Harald Welte <laforge@osmocom.org> | 2020-08-12 12:26:29 +0200 |
|---|---|---|
| committer | laforge <laforge@osmocom.org> | 2020-08-13 15:01:58 +0000 |
| commit | 306a51dd306733daba965c59735cb9c5c419b609 (patch) | |
| tree | 94c2f75cc320f64b5395d316d01c66658d979195 /jenkins-common.sh | |
| parent | 7b5248b464c0d054b6410d2fd14c87283d8f8977 (diff) | |
Enable IPv6 in docker networking
We previously only allocated IPv4 sub-nets to the network segments
created with 'docker network'. Let's fix that by assigning both
IPv4 and IPv6 address ranges to each docker network.
Related: OS#4700
Change-Id: I8802208fddcce1ffa57e5626575d23d02b320d99
Diffstat (limited to 'jenkins-common.sh')
| -rw-r--r-- | jenkins-common.sh | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/jenkins-common.sh b/jenkins-common.sh index 64ec0bb..2993767 100644 --- a/jenkins-common.sh +++ b/jenkins-common.sh @@ -87,8 +87,10 @@ network_create() { network_clean network_remove fi + SUB4="172.18.$NET.0/24" + SUB6="fd02:db8:$NET::/64" echo Creating network $NET_NAME - docker network create --internal --subnet $NET $NET_NAME + docker network create --internal --subnet $SUB4 --ipv6 --subnet $SUB6 $NET_NAME } network_remove() { |