Hey guys, im writing here because i’m really out of options and ideas. I have been trying to set up my lemmy instance in docker put i keep failing at the first step. I have filled every {{}} detail and still getting this error:
The Compose file ‘./docker-compose.yml’ is invalid because: Invalid top-level property “x-logging”. Valid top-level sections for this Compose file are: version, services, networks, volumes, secrets, configs, and extensions starting with “x-”.
You might be seeing this error because you’re using the wrong Compose file version. Either specify a supported version (e.g “2.2” or “3.3”) and place your service definitions under the
services
key, or omit theversion
key and place your service definitions at the root of the file to use version 1.
I have tried to edit the version number, even deleting it but then im getting this:
The Compose file ‘./docker-compose.yml’ is invalid because: Unsupported config option for x-logging: ‘options’ Unsupported config option for services: ‘proxy’
Do you have any idea?
Edit: Thank you all for the ideas. Actually the docker compose up -d solved it!
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Alright now im getting
There was an error on the server. Try refreshing your browser. If that doesn’t work, come back at a later time. If the problem persists, you can seek help in the Lemmy support community or Lemmy Matrix room.
but thats progress
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.Yeah I figured some port was not enabled