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
serviceskey, or omit theversionkey 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!
Here is my docker-compose.yml
spoiler
version: “3.7”
services: proxy: image: nginx:1-alpine ports: # actual and only port facing any connection from outside # Note, change the left number if port 1236 is already in use on your system # You could use port 80 if you won’t use a reverse proxy - “8536:8536” volumes: - ./nginx_internal.conf:/etc/nginx/nginx.conf:ro,Z restart: always depends_on: - pictrs - lemmy-ui
lemmy: image: dessalines/lemmy:latest hostname: lemmy restart: always environment: - RUST_LOG=“warn” volumes: - ./lemmy.hjson:/config/config.hjson:Z depends_on: - postgres - pictrs
lemmy-ui: image: dessalines/lemmy-ui:latest environment: - LEMMY_UI_LEMMY_INTERNAL_HOST=lemmy:8536 - LEMMY_UI_LEMMY_EXTERNAL_HOST=* - LEMMY_UI_HTTPS=true volumes: - ./volumes/lemmy-ui/extra_themes:/app/extra_themes depends_on: - lemmy restart: always
pictrs:
image: asonix/pictrs:0.4.0-rc.7
# this needs to match the pictrs url in lemmy.hjson
hostname: pictrs
# we can set options to pictrs like this, here we set max. image size and forced format for conversion
# entrypoint: /sbin/tini – /usr/local/bin/pict-rs -p /mnt -m 4 --image-format webp
environment:
- PICTRS_OPENTELEMETRY_URL=http://otel:4137
- PICTRS__API_KEY=lemmy1234
- RUST_LOG=debug
- RUST_BACKTRACE=full
- PICTRS__MEDIA__VIDEO_CODEC=vp9
- PICTRS__MEDIA__GIF__MAX_WIDTH=256
- PICTRS__MEDIA__GIF__MAX_HEIGHT=256
- PICTRS__MEDIA__GIF__MAX_AREA=65536
- PICTRS__MEDIA__GIF__MAX_FRAME_COUNT=400
user: 991:991
volumes:
- ./volumes/pictrs:/mnt:Z
restart: always
deploy:
resources:
limits:
memory: 690m
postgres:
image: postgres:15-alpine
hostname: postgres
environment:
- POSTGRES_USER=lemmy
- POSTGRES_PASSWORD=lemmy1234
- POSTGRES_DB=lemmy
volumes:
- ./volumes/postgres:/var/lib/postgresql/data:Z
- ./customPostgresql.conf:/etc/postgresql.conf
restart: always
postfix: image: mwader/postfix-relay environment: - POSTFIX_myhostname=lemmy.domain.com restart: “always”
This looks good to me. I suspect the problem is not with the compose file itself, but in the tool you’re invoking - something must be wrong with docker-compose. Try using docker compose up -d instead of docker-compose up -d (requires Docker v20.10.13+).
Posting output of docker-compose version, docker version and docker compose version may shine some light on this.
docker compose up -d
Jesus man that was it. docker compose up -d solved it. Thank you so much
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.
Alright now im getting
Error!
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 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.
where did you install Docker from? is it the docker repo or somewhere else?
Edit: check this out - https://docs.docker.com/engine/install/centos/
