Unnecessary instructions in the installation guide via Docker

The recommended way to install Seafile is via Docker. I follow this guide:
I don’t use Ubuntu, I use Debian. So I go here instead:


After that, Docker is installed and docker run hello-world works.

After that comes the step to install docker-compose. However, this deletes the previously installed packages containerd.io, docker-ce, docker-ce-cli and docker-ce-rootless-extras. Docker.io and containerd from the Debian repository including dependent libraries are installed for this purpose. The download.docker.com repository does not contain the docker-compose package.

Hello-World is still running, but I had to first delete the /var/lib/docker directory and restart docker.io.

I downloaded the docker-compose.yml file, adjusted it and ran docker-compose up -d . I can start the web interface and work with Seafile.

So why this detour via the foreign repository when Debian already contains everything that is necessary?

Can’t you just run pip install for docker-compose?

Is docker-compose a python module? I don’t think.

In the meantime I found out that you can either work with the Docker packages that comes with Debian or with a version from download.docker.com. If you use the latter, you cannot install the docker-compose package from Debian, but on download.docker.com it is not found in the package repository.

Either you download the binary from github or you work with the docker-compose-plugin. The latter is the package name that you have to install. This makes Compose a Docker command.

Instead of typing “docker-compose” then simply use “docker compose” (without -).

I don’t know whether Docker from the Debian repository or the Docker repository is better. The version in Debian Bullseye is 20.10.5, the one in Docker repository is 20.10.23.

Um, yeah…but…

Just like the layer squashing stuff is Python… innit?

I think that’s pretty standard across distros; I’ve been doing that for years now with Ubuntu and Rhel based distros as well.

That’a if you’re running a certain version or higher. I didn’t have to download anything to get it …

I would assume that depends on your definition of better. :slightly_smiling_face: I’m sure the SA’s who want to never touch q package unless it’s a security update – debian repos are far better.
If you’re someone who wants current and/or cutting edge expermimental features – docker’s repo’s are the only option.

FWIW i think it’s in the core or an experimental feature – commands that were once only possible with docker - are now possible with docker compose, e.g. docker compose run