Nicolas De loof
Nicolas De loof
As you run `docker compose -f third_party/netbox-docker/docker-compose.yml ...` the project directory is set to the parent folder of this first compose file (`third_party/netbox-docker`) and so relative paths are resolved based...
There's indeed a bug to be fixed here, but I wonder: how did you ended finding this ? Seems it doesn't make any sense to have a null service being...
I proposed a fix as https://github.com/compose-spec/compose-go/pull/547/commits/25f05966ff47ce7530d174ab46c274a1f39381e9
@luciangabor ok, that's an unexpected pattern
AFAIK networks created on a swarm cluster are only created on worker node "on first usage" by a swarm service. As compose does not integrate with swarm, it require such...
The code actually ignores checking for network existence as long as it is declared both `external` and with `driver: overlay`. IIRC we wanted here to avoid not detecting a missing...
I don't understand what's wrong here then :'(
> Is there a specific version of Docker or Docker Compose where the integration of health checks with depends_on (service_healthy condition) is known to work consistently? Docker compose v2.x supports...
Would you mind offering a pull-request to fix this ?
Tested with latest codebase, and I get the expected result: ``` Attaching to test-1 test-1 | 1 test-1 | 1 test-1 exited with code 0 ``` Can you please upgrade...