Generated docker compose command fails

[ignapas]

Getting the following error when using the docker_services fixture

Exception: Command docker compose -f "/tmp/pytest-of-xxx/pytest-1/docker-compose.yml" -p "pytest155540" up --build -d returned 125: """unknown shorthand flag: 'f' in -f

Using docker 20.10.17, could this be the problem?
Thanks

[pshyshko]

I resolved this by simply upgrading to docker-compose v2 on VM.

$ sudo apt update
$ sudo apt install docker-compose-plugin

[ntr-switchdin]

myself and another team member get this on MacOS:

~ -> docker info
Client:
 Version:    26.1.4
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.14.1-desktop.1
    Path:     /Users/ntr/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.27.1-desktop.1
    Path:     /Users/ntr/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.32
    Path:     /Users/ntr/.docker/cli-plugins/docker-debug
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     /Users/ntr/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.24
    Path:     /Users/ntr/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     /Users/ntr/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.2.0
    Path:     /Users/ntr/.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/ntr/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.9.3
    Path:     /Users/ntr/.docker/cli-plugins/docker-scout

Server:
 Containers: 14
  Running: 0
  Paused: 0
  Stopped: 14
 Images: 249
 Server Version: 26.1.4
 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 splunk syslog
 Swarm: inactive
 Runtimes: runc io.containerd.runc.v2
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: d2d58213f83a351ca8f528a95fbd145f5654e957
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
  seccomp
   Profile: unconfined
  cgroupns
 Kernel Version: 6.6.31-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 8
 Total Memory: 7.657GiB
 Name: docker-desktop
 ID: a657bbf3-e6fa-4f45-abf1-0bcc6f10ff35
 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
 Labels:
  com.docker.desktop.address=unix:///Users/me/Library/Containers/com.docker.docker/Data/docker-cli.sock
 Experimental: false
 Insecure Registries:
  hubproxy.docker.internal:5555
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: daemon is not using the default seccomp profile

[ntr-switchdin]

TLDR

Try the dmg version of docker desktop if on MacOS

Following on from my above comment:

After running docker info from pytest-docker I noticed that the compose client plugin (along with all the others) was missing from the output.

On a whim I changed from my brew installed version of docker to the dmg version of docker desktop, cycled it from the user bin location in settings back to system wide and this issue was resolved.

I can't say for sure which step resolved it, and unfortunately it's a bit hard for me to go back and test.
Additionally our pytest runs from pants within a nix setup, which likely was having some effect on the paths available to pytest-docker too.