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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.2.0
• Component/s: docker

Environment

• Docker version 20.10.17, build 100c701
• Docker Compose version v2.6.0

• Flags: Patch
• Assignee: Shuhei Yamasaki
• Reporter: Shuhei Yamasaki
• Created: 25/Sep/22 08:10
• Updated: 28/Sep/22 00:33
• Resolved: 28/Sep/22 00:33

Description

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.

$ docker network ls
NETWORK ID     NAME      DRIVER    SCOPE
208018a555e0   bridge    bridge    local
579b74682a38   host      host      local
0a52641d5e77   none      null      local

2. Create cluster and delete three times.

$ ./docker-hadoop.sh -C config_centos-7.yaml -c 3 -k "zookeeper"  -L
...(snip)...
$ ./docker-hadoop.sh -d
...(snip)...

3. Show resource again.

$ 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

Issue Links

• links to: GitHub pull request #1026