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.
this post was submitted on 26 Jun 2023
2 points (100.0% liked)
Lemmy Support
4652 readers
1 users here now
Support / questions about Lemmy.
founded 5 years ago
MODERATORS
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?