Skip to content
This repository has been archived by the owner on Nov 27, 2023. It is now read-only.

"down -v" does not remove volumes #1658

Closed
kiview opened this issue May 10, 2021 · 1 comment
Closed

"down -v" does not remove volumes #1658

kiview opened this issue May 10, 2021 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@kiview
Copy link

kiview commented May 10, 2021

Description

Running docker compose down -v does not remove volumes.

Steps to reproduce the issue:
Use a compose file with a volume:

services:
   alpine:
     image: alpine:latest
     volumes:
      - my_data:/var/lib/mysql

volumes:
    my_data: {}

Describe the results you received:

$ docker compose down -v
[+] Running 2/2
 ⠿ Container compose_alpine_1  Removed                                                                                                                                       0.0s
 ⠿ Network compose_default     Removed   

$ docker compose down --volumes
[+] Running 1/0
 ⠿ compose  Warning: No resource found to remove     

Describe the results you expected:

Running docker compose down -v should act identical to docker-compose down -v.

$ docker-compose down -v
Removing compose_alpine_1 ... done
Removing network compose_default
Removing volume compose_my_data

Output of docker version:

Client: Docker Engine - Community
 Cloud integration: 1.0.14
 Version:           20.10.6
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        370c289
 Built:             Fri Apr  9 22:46:45 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.6
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       8728dd2
  Built:            Fri Apr  9 22:44:56 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.4
  GitCommit:        05f951a3781f4f2c1911b05e61c160e9c30eaa8e
 runc:
  Version:          1.0.0-rc93
  GitCommit:        12644e614e25b05da6fd08a38ffa0cfe1903fdec
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Output of docker context show:
You can also run docker context inspect context-name to give us more details but don't forget to remove sensitive content.

default

Output of docker info:

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)
  compose: Docker Compose (Docker Inc., 2.0.0-beta.1)
  scan: Docker Scan (Docker Inc., v0.8.0)

Server:
 Containers: 21
  Running: 0
  Paused: 0
  Stopped: 21
 Images: 71
 Server Version: 20.10.6
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 05f951a3781f4f2c1911b05e61c160e9c30eaa8e
 runc version: 12644e614e25b05da6fd08a38ffa0cfe1903fdec
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 4.19.104-microsoft-standard
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 15.64GiB
 Name: docker-desktop
 ID: IIK6:QLHI:DCRW:UOKT:IK6M:4YNG:LBP3:VLNR:VSRZ:GEZW:B7A4:DLL4
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

Additional environment details (AWS ECS, Azure ACI, local, etc.):
Running inside WSL2.

@ndeloof ndeloof added the duplicate This issue or pull request already exists label May 10, 2021
@ndeloof
Copy link
Collaborator

ndeloof commented May 10, 2021

This has been fixed already, see #1599

@ndeloof ndeloof closed this as completed May 10, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants