-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Description
BUG REPORT INFORMATION
When I run "docker compose start " all services in docker-compose.yml (attached as txt) start, instead of the specified one.
I have moved a docker-compose.yml I had on a previous mac to a new Mac M1 and after I reinstalled docker it seems that "docker compose start " starts all services in the yml instead of the specified one. I also tried removing old images and pulling the new arm one and I still have the same issue. Other than this the services work fine.
Steps to reproduce the issue:
- docker compose up -d
- docker compose down
- docker compose start
Describe the results you received:
When I run "docker compose start " all services start
Describe the results you expected:
Command "docker compose start " should start only the specified service
Additional information you deem important (e.g. issue happens only occasionally):
Issue happens everytime I run "docker compose start "
Output of docker compose version:
Docker Compose version v2.10.2
Output of docker info:
Client:
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc., v0.9.1)
compose: Docker Compose (Docker Inc., v2.10.2)
extension: Manages Docker extensions (Docker Inc., v0.2.9)
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0)
scan: Docker Scan (Docker Inc., v0.19.0)
Server:
Containers: 7
Running: 0
Paused: 0
Stopped: 7
Images: 7
Server Version: 20.10.17
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: 2
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: 9cd3357b7fd7218e4aec3eae239db1f68a5a6ec6
runc version: v1.1.4-0-g5fd4c4d
init version: de40ad0
Security Options:
seccomp
Profile: default
cgroupns
Kernel Version: 5.10.124-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: aarch64
CPUs: 4
Total Memory: 7.765GiB
Name: docker-desktop
ID: SC5C:UTLO:7IWG:SQPN:CWR6:47KZ:5NAB:4XBT:2RIJ:3PTL:KZBE:YOR5
Docker Root Dir: /var/lib/docker
Debug Mode: true
File Descriptors: 48
Goroutines: 52
System Time: 2022-09-05T05:06:01.049054799Z
EventsListeners: 5
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5000
127.0.0.0/8
Live Restore Enabled: false
Additional environment details:
MacBook Pro M1
MacOS Monterey 12.5.1 (21G83)

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
