Update to last versions via docker compose

Support
1

Hello,

I installed Vikunja with docker compose. From time to time, I do docker compose pull and I restart Vikunja if new versions were found.

But I don’t know if it works: it seems to me the images on the hub are updated, but docker compose does not pull them. In fact, I do not see the new French translations but on GitHub (frontend), they are present.

Thank you!
Gilles.

2

Are you on the latest or unstable tag? unstable is built off the main branch and is what you see in the git repo. latest is the last stable release.

3

I have
image: vikunja/api
and
image: vikunja/frontend
in the docker-compose.yml file, without any mention to stable or unstable. I suppose it must be stable. :smiley:

Thank you!

4

Yes, if you don’t specify a tag it will pull :latest which always points to the last stable release.

There has been a new release in the meantime, you might want to update again.

There’s an article in the docs explaining the different versions: Versions | Vikunja

5

Just wanted to chime in that when running sudo docker inspect vikunja-api-1, there is not label information that specifies the version number. Maybe this is something that should be added?

6

There was a discussion elsewere about this recently: Feature request: Add opencontainer labels to Docker images · Issue #308 · go-vikunja/vikunja · GitHub

7

Hi, I just tried several time to update the docker image but I am “stuck” in Version: v0.23.0 when it should update to at least 24, right?

I used just vikunja/vikunja, but tried :latest and :0.24, with 0.24 it broke the app.

8

So you’ve pulled the :latest docker image but only got version 0.23.0?

9

Yes, exactly. I am using locker compose if that helps.

10

Can you share your docker compose file?

Does it work when you set the tag explicitly?

11

This is the docker compose file:

version: '3'

services:
 api:
   image: vikunja/vikunja
   environment:
    VIKUNJA_SERVICE_JWTSECRET: xxxx
    VIKUNJA_SERVICE_PUBLICURL: xxxx
    VIKUNJA_DATABASE_PATH: /db/vikunja.db
    VIKUNJA_MAILER_ENABLED: 1
    VIKUNJA_MAILER_FORCESSL: 1
    VIKUNJA_MAILER_HOST: xxxx
    VIKUNJA_MAILER_PORT: 465
    VIKUNJA_MAILER_USERNAME: xxxx
    VIKUNJA_MAILER_PASSWORD: xxxxx
    VIKUNJA_MAILER_FROMEMAIL: xxxxx
    # VIKUNJA_LOG_LEVEL: DEBUG
   ports:
     - 3456:3456
   volumes:
     - ./files:/app/vikunja/files
     - ./db:/db
   restart: unless-stopped

I tried to pull vikunja:0.24 but it got stuck in migrating, the web did not work and when it reverted the version to :latest (0.23 in my case) it “corrupted” de database somehow, I needed to pull a backup.

The thing is I tried this in another pc and it worked as expected, pulling the version 24.4. :dizzy_face:

Both pcs run Ubuntu 22.04.5 LTS.

So it must be something with my server, but can´t figure it out. It is an old laptop: Intel(R) Core™ i3-2367M CPU @ 1.40GHz

Thank you very much!

12

How did you pull the image? Does it work if you remove the image and pull again?

You mean it took a while during migration without seeming to do anything? That might be normal, especially if you have a lot of data.

1 Like
13

I changed vikunja:vikunja into vikunja:vikunja:0.24

I tried removing the image, all vikunja images, and pulling again and it did work using vikunja:vikunja!

Thank you!
Is this expected? should I always remove the old images before updating?

14

Glad it works now!

It’s not expected. You should be able to pull the image right away without clearing caches.

1 Like