search

docker-archive / for-aws

92 stars 26 forks source link

Internal network does not get created as configured #79

Closed Deepak-Vohra closed 7 years ago

Deepak-Vohra commented 7 years ago

Expected behavior

An internal overlay network to get created

Actual behavior

Internal network gets created but not usable and not configured as overlay driver network

Steps to reproduce the behavior

  1. ...Create an internal network
  2. ...List the networks.
~ $ docker network rm hello-world-network
hello-world-network
~ $ docker network create \
>    --subnet=10.0.0.0/16 \
>    --gateway=10.0.0.100 \
>    --internal \
>    --label HelloWorldService \
>    --ip-range=10.0.1.0/24 \
>   --driver overlay \
>   hello-world-network
wozpfgo8vbmhmw576gxa3hymu
~ $ docker network ls
NETWORK ID          NAME                  DRIVER              SCOPE
34a5f77de8cf        bridge                bridge              local
0e06b811a613        docker_gwbridge       bridge              local
wozpfgo8vbmh        hello-world-network                       swarm
6763ebad69cf        host                  host                local
e41an60iwval        ingress               overlay             swarm
mkileuo6ve32        mysql-network         overlay             swarm
qwgb1lwycgvo        mysql-network-2       overlay             swarm
eb7399d3ffdd        none                  null                local
aqppoe3qpy6m        overlay-network-2     overlay             swarm
Deepak-Vohra commented 7 years ago

Internal network gets created on retesting. Issue may be a closed as a non issue.