Container says updated to 2.2.2 but serverversion shows 1.0.0.rc3

Support
1

Hi there,

I’ve installed a fresh version of vikunja 3 or 4 days ago.

my setup is a rootless podman environment and the container is started via systemd Quadlet file.

Today I discovered, that my frontend is version 1.0.0.rc3, because I installed the app from the playstore on my phone and I can’t connect because of this outdated version.

But my image was latest. I also changed my image tag to 2.2.2 and my frontend is still 1.0.0.rc3.

Yes I’ve cleared my browser cache :slight_smile:

this are my pulled images:

podman images -a
REPOSITORY                                  TAG         IMAGE ID      CREATED        SIZE
docker.io/vikunja/vikunja                   latest      214d1fcc189b  3 days ago     82.8 MB
docker.io/vikunja/vikunja                   2.2.2       214d1fcc189b  3 days ago     82.8 MB

and this is my Quadlet-file

[Container]

Image=docker.io/vikunja/vikunja:2.2.2
ContainerName=vikunja
AutoUpdate=registry

Volume=vikunja:/app/vikunja:Z
Volume=vikunja-db:/db:Z



PublishPort=3456:3456



Environment=VIKUNJA_DATABASE_TYPE=sqlite
Environment=VIKUNJA_DATABASE_PATH=/db/vikunja.db
Environment=VIKUNJA_FILES_BASEPATH=/app/vikunja/files



Environment=VIKUNJA_SERVICE_JWTSECRET=XXXX


Environment=VIKUNJA_SERVICE_PUBLICURL=XXXX
#Mailer und Service
Environment=VIKUNJA_SERVICE_ENABLETASKATTACHMENTS=1
Environment=VIKUNJA_SERVICE_ENABLEEMAILREMINDERS=1
Environment=VIKUNJA_SERVICE_ENABLEREGISTRATION=0
Environment=VIKUNJA_MAILER_ENABLED=1
Environment=VIKUNJA_MAILER_FORCESSL=1
Environment=VIKUNJA_MAILER_HOST=XXXX
Environment=VIKUNJA_MAILER_PORT=465 
Environment=VIKUNJA_MAILER_USERNAME=XXXX
Environment=VIKUNJA_MAILER_PASSWORD=XXXX 
Environment=VIKUNJA_MAILER_FROMEMAIL=XXXX

[Service]
Restart=always
RestartSec=10s


TimeoutStartSec=300

[Install]
WantedBy=default.target