Description
unexpected 'no such service' error when --no-deps and volumes_from used together
Steps To Reproduce
- Create the following
docker-compose.yaml:
services:
app:
image: busybox
command:
- "sleep"
- "1000"
volumes_from:
- db
db:
image: mysql:5.7.37
environment:
MYSQL_ROOT_PASSWORD: root
MYSQL_DATABASE: DOCKERDB
volumes:
- db-data:/var/lib/mysql
volumes:
db-data:
- Run
docker compose up -d
- Run
docker compose up --no-deps app
Expected Result:
The app service starts successfully, without restarting db.
Actual result:
docker compose up --no-deps app
no such service: db
Compose Version
docker compose version
Docker Compose version v2.21.0-desktop.1
Docker Environment
Client: Docker Engine - Community
Version: 24.0.5
Context: desktop-linux
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.11.0-cloud-driver+002
Path: /home/nick/.docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.21.0-desktop.1
Path: /usr/lib/docker/cli-plugins/docker-compose
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.0
Path: /usr/lib/docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.20
Path: /usr/lib/docker/cli-plugins/docker-extension
harmonia: A brief description of Harmonia (Docker Inc.)
Version: 1014447
Path: /home/nick/.docker/cli-plugins/docker-harmonia
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v0.1.0-beta.7
Path: /usr/lib/docker/cli-plugins/docker-init
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: /usr/lib/docker/cli-plugins/docker-sbom
scan: Docker Scan (Docker Inc.)
Version: v0.26.0
Path: /usr/lib/docker/cli-plugins/docker-scan
scout: Command line tool for Docker Scout (Docker Inc.)
Version: 0.24.1
Path: /usr/lib/docker/cli-plugins/docker-scout
sleep: (Docker Inc.)
Version: 0.1.0
Path: /home/nick/.docker/cli-plugins/docker-sleep
Server:
Containers: 6
Running: 4
Paused: 0
Stopped: 2
Images: 5
Server Version: master
Storage Driver: stargz
driver-type: io.containerd.snapshotter.v1
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 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 8165feabfdfe38c65b599c4993d227328c231fca
runc version: v1.1.8-0-g82f18fe
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
cgroupns
Kernel Version: 6.3.13-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 3.65GiB
Name: docker-desktop
ID: a92cef06-564f-4766-91bd-bc9e839af9fa
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Experimental: false
Insecure Registries:
registry:1234
hubproxy.docker.internal:5555
127.0.0.0/8
Live Restore Enabled: false
WARNING: daemon is not using the default seccomp profile
Anything else?
This repro case has been boiled down from tilt-dev/tilt#6220
Description
unexpected 'no such service' error when --no-deps and volumes_from used together
Steps To Reproduce
docker-compose.yaml:docker compose up -ddocker compose up --no-deps appExpected Result:
The app service starts successfully, without restarting db.
Actual result:
Compose Version
Docker Environment
Anything else?
This repro case has been boiled down from tilt-dev/tilt#6220