Lemmy Support

4650 readers

25 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago

MODERATORS

dessalines@lemmy.ml

Docker extension for x-logging directive (beehaw.org)

submitted 1 year ago by japps13@beehaw.org to c/lemmy_support@lemmy.ml

2 comments fedilink hide all child comments

I am trying to install Lemmy with Docker. I followed the instructions here but I get the following error message:

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-".

It says extensions start with "x-", so I assume that I need to install some extension regarding to logging. This is straightforward, but apparently I haven't been able to find the right keywords to ask Google...

Could anyone point me to this required extension and how to install it?

you are viewing a single comment's thread
view the rest of the comments

[–] ActuallyRuben@actuallyruben.nl 1 points 1 year ago (1 children)

Try updating your docker-compose version. Any top-level property starting with x- should be accepted as an extension, whether compose can understand it's contents or not. In this case the x-logging section is used as a fragment to set up default logging settings for each service.

[–] japps13@beehaw.org 1 points 1 year ago

The doc says

Make sure you have both docker and docker-compose(>=1.24.0) installed. On Ubuntu, just run apt install docker-compose docker.io.

and I have,

$ docker-compose -v
docker-compose version 1.25.0, build unknown

However, I don't have docker.io, because

The following packages have unmet dependencies:
 containerd.io : Conflicts: containerd
                 Conflicts: runc
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

I am a bit wary about uninstalling containerd and runc, because I have a few other docker containers running on the VPS and I don't want to break them. What is the difference between docker.io and the regular docker package? Is it why docker-compose throws an error?