Closed colin3131 closed 1 year ago
Figured it out, lavalink starts up a lot slower than lavamusic. Restarting lavamusic container did the trick. @brblacky I'm not too experienced with docker but if there's a way to add a container startup delay in the docker-compose file, that could solve this issue.
With all required environment variables set (TOKEN, PREFIX, OWNER_IDS, CLIENT_ID, GUILD_ID, PRODUCTION), docker-composed did not work out of the box, none of the nodes could communicate with one another using the defined URLs. I had to change the following variables (to use pod addresses rather than localhost):
I'm still running into an issue where no nodes are created, no errors appearing in the logs aside from when I run the play command
Database connects successfully, and lavamusic can resolve and send http over the lavalink URL I've added, so that's not the issue.
For reference, this is the current version of the docker compose file I'm using: