Description
When I run docker compose restart <service> on a service that has profiles set to a non-empty list, the command fails with no such service: <service>. I would expect the single service to restart successfully in this case.
By contrast, the following all work just fine:
docker compose up <service> when the service belongs to a profiledocker compose down <service> when the service belongs to a profiledocker compose restart <service> when the service does not belong to a profile.
Steps To Reproduce
- On MacOS Ventura 13.5.1 with Docker Desktop for Mac 4.21.1 (Compose v2.19.1)
- With this docker-compose.yml:
version: "3.9"
services:
foo:
profiles:
- a
image: "bash"
command: ["sleep", "inf"]
bar:
image: "bash"
command: ["sleep", "inf"]
- Run
docker compose up -d and then docker restart foo
- See error
no such service: foo
Compose Version
Docker Compose version v2.19.1
Docker Environment
Client:
Version: 24.0.2
Context: desktop-linux
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.11.0
Path: /Users/nfeldman/.docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.19.1
Path: /Users/nfeldman/.docker/cli-plugins/docker-compose
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.0
Path: /Users/nfeldman/.docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.20
Path: /Users/nfeldman/.docker/cli-plugins/docker-extension
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v0.1.0-beta.6
Path: /Users/nfeldman/.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: /Users/nfeldman/.docker/cli-plugins/docker-sbom
scan: Docker Scan (Docker Inc.)
Version: v0.26.0
Path: /Users/nfeldman/.docker/cli-plugins/docker-scan
scout: Command line tool for Docker Scout (Docker Inc.)
Version: 0.16.1
Path: /Users/nfeldman/.docker/cli-plugins/docker-scout
Server:
Containers: 24
Running: 18
Paused: 0
Stopped: 6
Images: 22
Server Version: 24.0.2
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: 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: 3dce8eb055cbb6872793272b4f20ed16117344f8
runc version: v1.1.7-0-g860f061
init version: de40ad0
Security Options:
seccomp
Profile: builtin
cgroupns
Kernel Version: 5.15.49-linuxkit-pr
Operating System: Docker Desktop
OSType: linux
Architecture: aarch64
CPUs: 5
Total Memory: 7.667GiB
Name: docker-desktop
ID: 0028c1ea-297a-4966-9b59-b4625390b198
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:
hubproxy.docker.internal:5555
127.0.0.0/8
Live Restore Enabled: false
Anything else?
No response
Description
When I run
docker compose restart <service>on a service that hasprofilesset to a non-empty list, the command fails withno such service: <service>. I would expect the single service to restart successfully in this case.By contrast, the following all work just fine:
docker compose up <service>when the service belongs to a profiledocker compose down <service>when the service belongs to a profiledocker compose restart <service>when the service does not belong to a profile.Steps To Reproduce
docker compose up -dand thendocker restart foono such service: fooCompose Version
Docker Environment
Anything else?
No response