Docker - Minor Upgrade

Seafile Server
1

Hi

I am running Seafile CE 13.0.25 with Docker.

There is 13.0.28 available and I would like to update to it.

I am reading the Manual for doing a Minor Upgrade with docker.

It says:

For maintenance upgrade, like from version 10.0.1 to version 10.0.4, just download the new image, stop the old docker container, modify the Seafile image version in docker-compose.yml to the new version, then start with docker compose up.

I don’t believe there is a docker-compose.yml file anymore.

The .env file refers to all the latest Seafile images:

Images

SEAFILE_IMAGE=seafileltd/seafile-mc:13.0-latest
SEAFILE_DB_IMAGE=mariadb:10.11
SEAFILE_REDIS_IMAGE=redis
SEAFILE_CADDY_IMAGE=lucaslorentz/caddy-docker-proxy:2.12-alpine
SEADOC_IMAGE=seafileltd/sdoc-server:2.0-latest
NOTIFICATION_SERVER_IMAGE=seafileltd/notification-server:13.0-latest
MD_IMAGE=seafileltd/seafile-md-server:13.0-latest

So I did an docker compose down and then docker compose up -d , hoping that it would pull the newest docker image.

But it came back up as 13.0.25, not latest 13.0.28

Can someone guide me into the right direction for an updated manual or just let me know what I need to do for a minor upgrade, please.

This is probably my little knowledge on docker in general. But I will get there :slight_smile:

Thanks a lot in advance,

Chris

2

The process you describe is correct. When you say you are running 13.0.25, where are you looking to decide this?

There are several things you can run in Docker to check whether you are pulling the correct (or any) images.

docker compose pull

will pull all the images for services in your server stack.

docker compose pull seafileltd/seafile-mc:13.0-latest

will pull only the latest Seafile Server v.13 image.

To inspect downloaded images you can use:

sudo docker images -a

To inspect containers in use:

sudo docker ps -a

Is it possible that your Seafile Server yaml file specifies one version of Seafile while your .env file has another that is not being referenced?

3

Thanks @mercury for taking the time to answer, that solved it.

I haven’t done “docker compose pull” before.
I thought the script does this automatically and I didn’t know.

I have tried it and now it works.

docker compose pull
docker compose down
docker compose up -d

Great how simple it is!
Maybe it makes sense that this is being added to the manual (even if so simple).

Thanks again !

Edit: As a heads up: Once Seafile CE 14 is out officially, I am gonna ask again how to upgrade to that one :blush:
Edit2: Well, that’s actually well documented. That should be alright :slight_smile:

4

I’m glad that your problem is resolved but your issue is still unsolved for me. As I understand it, if you shutdown the stack it should clear the deck (so to speak) for the update that occurs when you start the server stack again (docker compose up -d) assuming the latest version of the image file is being specified and pulled. Any idea why that might not have happened?

5

That behavior that you describe is what I had expected as well.

I don’t know why it doesn’t pull the latest image but leaves the 13.0.25

It’s probably good in case you want to adjust something to the server but don’t yet want to update to a next version.