Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] docker compose run --no-deps fails to build and run a service with dependencies #10808

Closed
bjorgvino opened this issue Jul 15, 2023 · 1 comment

Comments

@bjorgvino
Copy link

bjorgvino commented Jul 15, 2023

Description

I noticed that when I docker compose run --no-deps a service that depends on another service it runs fine when the said service has already been built but fails when docker compose run needs to build it. It seems like this is triggered by the --no-deps flag because without it the service builds and runs just fine.

Steps To Reproduce

Here is a Dockerfile and docker-compose.yml to reproduce the issue.

Dockerfile:

FROM alpine:latest AS service1
CMD ["echo", "hello from service1"]

FROM alpine:latest AS service2
CMD ["echo", "hello from service2"]

docker-compose.yml:

version: '3.6'
name: dcr-bug

services:
  service1:
    build:
      context: .
      dockerfile: Dockerfile
      target: service1

  service2:
    build:
      context: .
      dockerfile: Dockerfile
      target: service2
    depends_on:
      service1:
        condition: service_completed_successfully

Running docker compose run --no-deps service2 will fail with the following error:

[+] Creating 1/0
 ✔ Network dcr-bug_default  Created                                                                                                                                                                                       0.0s
[+] Building 0.0s (0/0)
service service1 is required by service2 but is disabled. Can be enabled by profiles []

Whereas running docker compose build service2 && docker compose run --no-deps service2 will give the expected output:

[+] Building 3.7s (6/6) FINISHED
...
[+] Creating 1/0
 ✔ Network dcr-bug_default  Created                                                                                                                                                                                       0.0s
hello from service2

Running docker compose run service2 works fine too, it will build and run both services without a problem.

Note: I used docker system prune -a to reset my environment when testing this.

Compose Version

> docker compose version
Docker Compose version v2.19.1

> docker-compose version
Docker Compose version v2.19.1

Docker Environment

Client: Docker Engine - Community
 Version:    24.0.2
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.11.0
    Path:     /Users/user/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.19.1
    Path:     /Users/user/.docker/cli-plugins/docker-compose
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/user/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.20
    Path:     /Users/user/.docker/cli-plugins/docker-extension
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v0.1.0-beta.6
    Path:     /Users/user/.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/user/.docker/cli-plugins/docker-sbom
  scan: Docker Scan (Docker Inc.)
    Version:  v0.26.0
    Path:     /Users/user/.docker/cli-plugins/docker-scan
  scout: Command line tool for Docker Scout (Docker Inc.)
    Version:  0.16.1
    Path:     /Users/user/.docker/cli-plugins/docker-scout

Server:
 Containers: 1
  Running: 0
  Paused: 0
  Stopped: 1
 Images: 1
 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: 4
 Total Memory: 14.63GiB
 Name: docker-desktop
 ID: b80f8422-b35f-40a7-a170-0fe5ed2ecdb9
 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

@ndeloof
Copy link
Contributor

ndeloof commented Jul 17, 2023

Closing as a duplicate for #10751

@ndeloof ndeloof closed this as completed Jul 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants