-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Closed
Labels
Description
Description
This happens with latest docker compose version. Let me explain using images.
Older version
Latest version
Is this expected with latest version..?
Steps To Reproduce
- Install older docker compose version like in the image and run as specified in the image.
- Install latests docker compose version and run as specified in the image.
Compose Version
older - 2.29.1
Latest - 2.32.0
Docker Environment
charankamarapu@lima:express-mongoose$ docker info
Client: Docker Engine - Community
Version: 27.4.1
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.19.3
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.32.0
Path: /home/charankamarapu.linux/.docker/cli-plugins/docker-compose
Server:
Containers: 3
Running: 0
Paused: 0
Stopped: 3
Images: 93
Server Version: 27.4.1
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 207ad711eabd375a01713109a8a197d197ff6542
runc version: v1.2.1-0-gd7735e38
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.1.0-28-cloud-arm64
Operating System: Debian GNU/Linux 12 (bookworm)
OSType: linux
Architecture: aarch64
CPUs: 4
Total Memory: 7.76GiB
Name: lima-debian
ID: 43682ee2-4ff7-4306-9493-ed6713cd0eb8
Docker Root Dir: /var/lib/docker
Debug Mode: false
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Anything else?
No response
gouravkrosx, chadyred, nehagup, charankamarapu and slayerjain