This means your docker-compose
is very outdated or even broken.
To give you some context, originally Docker Compose was a separate project. It’s a separate program called docker-compose
. It evolved for quite a while, and was eventually rewritten and included as a part of Docker itself, becaming a sub-command (docker compose
).
Just uninstall the old Compose (so it won’t cause you any issues) and keep only Docker.
This means Lemmy container is up and running, but there is some error on the backend that prevents it from functioning correctly. A pretty wild guess, but it’s probably something with the database.
docker compose logs
may tell a bit more about what’s going on. Check out this page https://join-lemmy.org/docs/administration/troubleshooting.html (just remember to replacedocker-compose
withdocker compose
- again, I specifically recommend to uninstalldocker-compose
so it won’t accidentally mess things up).If it’s not something obvious, one thing you may try is tear everything down (
docker compose down -v
), changelemmy:latest
tolemmy:0.18.1
in your Compose file, and try starting again. This will use explicit version number and it may help if thelatest
tag is not something we expect it to be. E.g. I had issues spinning up clean 0.17.4 - it had a bug in DB migrations that was supposed to be fixed in 0.18.