Container reported as exited if compose files uses anchors

[yewkay]

⚠️ Please verify that this bug has NOT been reported before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

If my docker compose files contains anchors the container will be reported as exited in dockge even when it's actually running
version: "3" services: base: &a1 image: container/image:latest env_file: .env ## Change this file for customized env variables volumes: - ./data/storage:/app/storage networks: - nginx-proxy rails: <<: *a1 depends_on: - postgres - redis ports: - 9100:3000 environment: - NODE_ENV=production - RAILS_ENV=production - INSTALLATION_ENV=docker entrypoint: docker/entrypoints/rails.sh command: - bundle - exec - rails - s - -p - "3000" - -b - 0.0.0.0 networks: - nginx-proxy sidekiq: <<: *a1 depends_on: - postgres - redis environment: - NODE_ENV=production - RAILS_ENV=production - INSTALLATION_ENV=docker command: - bundle - exec.....

👟 Reproduction steps

Create a compose file containing anchors

👀 Expected behavior

Dockge would report the container as active

😓 Actual Behavior

Container is reported as extied

Dockge Version

1.4.2

💻 Operating System and Arch

Linux

🌐 Browser

Chrome

🐋 Docker Version

Docker version 20.10.27

🟩 NodeJS Version

No response

📝 Relevant log output

No response