FYI: Broken on New Docker Compose

[gchallen]

trafficstars

I was tearing my hair out for a bit since I couldn't start my development Jitsi set up using docker compose up—i.e., using the new compose command added to the core Docker cli. However, after switching back to docker-compose up things started working again.

I'm fairly sure that this is a problem with the new compose command and not with the Jitsi docker-compose.yaml file. But I thought I would note it here in case someone else has the same problem.

[saghul]

What problem do you get? I didn't even know the had baked compose in!

[gchallen]

I'm getting the error about xmpp.meet.jitsi not resolving, similar to some recent problems people had experienced using code from the master branch. (One of the reasons it was so confusing.) I suspect that the new docker compose hasn't fully implemented certain docker-compose.yml features, so perhaps the alias isn't getting set properly for the prosody container? No clue. (I've noticed that docker compose also doesn't respect certain fields that docker-compose did, conspicuously it seems impossible to disable logging for a container using logging.driver: "none" which was possible in the past. So it doesn't seem feature complete yet.)

You should be able to reproduce easily.