[-] drdaeman@lemmy.zhukov.al 1 points 1 year ago

So you can comment, vote and save without jumping extra hoops (because you can only do this from your home instance)

[-] drdaeman@lemmy.zhukov.al 1 points 1 year ago* (last edited 1 year ago)

I'm not sure you understand me. What I wanted to say is that if APIs and protocols would be copyrightable, and SCO and Oracle would've won their respective lawsuits, the world would look so different (in regards to Free and Open Source Software) I'm not completely sure if Fediverse would be a thing.

[-] drdaeman@lemmy.zhukov.al 1 points 1 year ago

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 replace docker-compose with docker compose - again, I specifically recommend to uninstall docker-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), change lemmy:latest to lemmy:0.18.1 in your Compose file, and try starting again. This will use explicit version number and it may help if the latest 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.

view more: ‹ prev next ›

drdaeman

joined 1 year ago