🐞 Bug: depends_on not supported in compose.yaml

[vladaurosh]

Bug Description

It looks like depends_on is not supported in compose files in Arcane.
I have compose file with 2 services where second one depends on first one:

    depends_on:
      service_2:
        condition: service_healthy

Now, when I start project, first service is started correctly, but second one is in "created" state and never starts, and first one is healthy.
Running 'docker compose up -d' in the terminal correctly starts second container.

Steps To Reproduce

Create compose.yaml with 2 services and add

    depends_on:
      service_2:
        condition: service_healthy

Expected Behavior

Second container starts after first one becomes healthy.

Actual Behavior

Second service stays in created state.

Screenshots

No response

Arcane Version

1.11.0

Installation Method

Docker Compose (Recommended)

Environment Type

Remote Agent Mode

Database Type

SQLite (Default)

Operating System

Linux

Docker Version

29.1.2

Browser & Version

Chrome

Relevant Logs or Error Messages

Docker Compose Configuration

Environment Configuration (.env file)

Additional Context

No response

[kmendell]

@vladaurosh Can you try ghcr.io/getarcaneapp/arcane:depends-on please?

[vladaurosh]

Hey @kmendell Just tried that image (I had to build armv7 headless agent myself) but still no changes, second container is in created state.

[kmendell]

Can you provide the compose your using so I can test it out? Or a basic example? I was able to get the depends on to work but maybe I'm not using it the same way

[vladaurosh]

Hey @kmendell
Sure, here it is:

services:
  chrony1:
    image: simonrupf/chronyd:latest
    container_name: chrony1
    restart: unless-stopped
  chrony2:
    image: simonrupf/chronyd:latest
    container_name: chrony2
    restart: unless-stopped
    depends_on:
      chrony1:
        condition: service_healthy

This is running on agent server, if that is important. Though I have just tried on master server, and got the same result.