YAML sucks.
Replying to @drq@mastodon.ml
Docker, I want only one dependency container to have a condition so the service could start, not every one of them.
Replying to @drq@mastodon.ml
@drq I dont understand, why you hate yaml, if problem in docker?
Replying to @redume@gts.redume.lol
@redume Because it's YAML's implicit syntax problem.
That's what I actually hate the most about it: it's implicit to Hell and back. Yes, on a glance, the file looks lightweight, there's few words in there, but you have to just somehow "know" a lot of random stuff just to correct an attribute in it.
Replying to @drq@mastodon.ml
@drq You have several docker service, however you want to start one service? I dont understand you problem and what you want. I had no problem with yaml
Replying to @redume@gts.redume.lol
@redume I have one service dependant on the other two.
One has to quit before launching said service, the other should start before launching the service (which is the default behaviour).
So, I can't just put a colon on one of them and have it have a "service_completed_successfully" condition. So this:
```
depends_on:
backendb
launcher:
condition: service_completed_successfully
```
doesn't work. It reports a YAML error without much of a further explanation. Turns out (after googling and a cheeky little ChatGPT query), that I _have_ to have a condition on both of them, or neither:
```
depends_on:
backendb:
condition: service_started
launcher:
condition: service_completed_successfully
```
