How to skip the health check when starting a service?

[blissful sleet]

Our application involves P2P messaging and we'd like to start 2 containers (p1 and p2) that can communicate to each other. In other words, p1 needs to be able to reach p2 and vice versa.

I've tried making two containers that have service bindings to each other, and I've skipped the health check with WithExposedPort(26656, dagger.ContainerWithExposedPortOpts{ExperimentalSkipHealthcheck: true}). But it seems to be stuck waiting for the other to start.

I'd like to start both at the same time and have them be able to reach each other.

https://dagger.cloud/cordialsys/traces/02df3b679ea9ed1085118fea72aa6ec4

[urban loom]

👋 cyclic services are currently not supported. We're reworking the Services DX to make this possible in the near future. In the meantime the not so good stopgap to handle this use-case is to use a cachevolume between the two services and make the service create a file with its IP once it starts

This way that cache volume could be used as a sort of service discovery

cc @quaint vortex

[blissful sleet]

okay, perhaps the shared files could be valid /etc/hostsfiles, and each container could self-update their /etc/hosts