[jira] [Created] (BIGTOP-3828) Docker network resource continues to remain when use docker provisioner.

["Shuhei Yamasaki (Jira)" <ji...@apache.org>]

Shuhei Yamasaki created BIGTOP-3828:
---------------------------------------

             Summary: Docker network resource continues to remain when use docker provisioner.
                 Key: BIGTOP-3828
                 URL: https://issues.apache.org/jira/browse/BIGTOP-3828
             Project: Bigtop
          Issue Type: Bug
          Components: docker
         Environment: * Docker version 20.10.17, build 100c701
* Docker Compose version v2.6.0
            Reporter: Shuhei Yamasaki
            Assignee: Shuhei Yamasaki


The option -d or --destroy in docker-hadoop.sh can destroy cluster by provisioner id, but the network resource is remaining after deletion.

The steps to reproduce it is as follows...

1. First, show network resource of docker.
{code:sh}
$ docker network ls
NETWORK ID     NAME      DRIVER    SCOPE
208018a555e0   bridge    bridge    local
579b74682a38   host      host      local
0a52641d5e77   none      null      local
{code}
2. Create cluster and delete three times.
{code:sh}
$ ./docker-hadoop.sh -C config_centos-7.yaml -c 3 -k "zookeeper"  -L
...(snip)...
$ ./docker-hadoop.sh -d
...(snip)...
{code}
3. Show resource again.
{code:sh}
$ docker network ls
NETWORK ID     NAME                             DRIVER    SCOPE
9f8ae5b32e07   20220925_101530_r28800_default   bridge    local
7e7d6d783573   20220925_101945_r11393_default   bridge    local
ca9ffdc892ce   20220925_102302_r2728_default    bridge    local
208018a555e0   bridge                           bridge    local
579b74682a38   host                             host      local
0a52641d5e77   none                             null      local
{code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)