Bug Report: docker compose references a YAML file not present in the current working directory

Docker Engine Compose
,
1

Problem Description: Using MinIO as an example, both Directory A and Directory B contain their own compose.yaml for MinIO. Querying deployment status in Directory A unexpectedly reads resources from Directory B.
In fact, executing docker compose ps inside Directory A is supposed to only consume the local compose.yaml in the current directory, instead of picking up the compose.yaml from Directory B.

Screen Recording Log https://www.youtube.com/watch?v=oxdQhAmmMAo

root@442-app1:/tmp/minIO# docker info
Client: Docker Engine - Community
 Version:    29.7.2
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.36.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v5.5.0
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 16
  Running: 15
  Paused: 0
  Stopped: 1
 Images: 18
 Server Version: 29.7.2
 Storage Driver: overlayfs
  driver-type: io.containerd.snapshotter.v1
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 CDI spec directories:
  /etc/cdi
  /var/run/cdi
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: aad11006b869517fcd3009450b6f82da282e1a9b
 runc version: v1.4.3-0-gbb14dabe
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 7.0.0-30-generic
 Operating System: Ubuntu 26.04.1 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 104
 Total Memory: 123.3GiB
 Name: 442-app1
 ID: 990d0c9a-fd42-489e-a6d0-0cce156a73cf
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  ::1/128
  127.0.0.0/8
 Registry Mirrors:
  https://docker.1ms.run/
 Live Restore Enabled: false
 Firewall Backend: iptables
  EnableUserlandProxy: true
  UserlandProxyPath: /usr/bin/docker-proxy


root@442-app1:/tmp/minIO# cat /etc/os-release 
PRETTY_NAME="Ubuntu 26.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="26.04"
VERSION="26.04.1 LTS (Resolute Raccoon)"
VERSION_CODENAME=resolute
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=resolute
LOGO=ubuntu-logo
root@442-app1:/tmp/minIO#
2

As evidenced by the configuration file, the compose.yaml in Directory A does not utilize the tv label. However, when I list deployed resources from Directory A, Docker reports that resources tagged with tv are identifiable.

In Directory A, my compose.yaml has

services:
  minio-server:
    image: minio/minio:RELEASE.2025-09-07T16-13-09Z
    container_name: minio-server
    restart: unless-stopped
    networks:
      - minio
    ports:
      - "19000:9000"
      - "19001:9001"
    volumes:
      - minio-data:/data
    secrets:
      - minio_root_user
      - minio_root_password
    environment:
      # MinIO 原生支持 _FILE 后缀，自动读取 /run/secrets/ 下的文件内容
      - MINIO_ROOT_USER_FILE=/run/secrets/minio_root_user
      - MINIO_ROOT_PASSWORD_FILE=/run/secrets/minio_root_password
    healthcheck:
      test: ["CMD", "mc", "ready", "local"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 30s
    deploy:
      resources:
        limits:
          cpus: '2.0'
          memory: 4G
        reservations:
          cpus: '0.5'
          memory: 1G
    command: server /data --console-address ":9001"

  minio-console:
    image: zhuyifeiruichuang/georgmangold-console:dev1
    container_name: minio-console
    restart: unless-stopped
    networks:
      - minio
    ports:
      - "19090:9090"
    environment:
      - CONSOLE_MINIO_SERVER=http://minio-server:9000
    depends_on:
      minio-server:
        condition: service_healthy
    deploy:
      resources:
        limits:
          cpus: '2.0'
          memory: 2G
        reservations:
          cpus: '1.0'
          memory: 1G

secrets:
  minio_root_user:
    file: ./secrets/minio_root_user
  minio_root_password:
    file: ./secrets/minio_root_password

networks:
  minio:
    name: minio-net
    driver: bridge

volumes:
  minio-data:
    name: minio-data

In Directory B, my compose.yaml has

services:
  tv-minio:
    image: tv_minio:v2
    container_name: tv-minio
    restart: unless-stopped
    networks:
      - tv2_net
    ports:
      - "9100:9000"
      - "9101:9001"
    environment:
      MINIO_ROOT_USER: admin
      MINIO_ROOT_PASSWORD: "A1qaz@#$%"
    volumes:
      - tv-minio-data:/data
    command: server /data --console-address ":9001"

networks:
  tv2_net:
    name: tv-net
    external: true

volumes:
  tv-minio-data:
    name: tv-minio-data
3

sorry, it is my bad ,i should config name: projec1 as topiic in compose.yaml