Update 0.22 -> 0.24 on Synology NAS

Support
1

Hi,
I have been successfully running Vikunja 0.22 on my Synology NAS using Docker. I now want to update to 0.24 and have noticed that quite a few changes have been made.
My 0.22 version is running with a MySQL database that is hosted on the Synology.

In the installation examples for Docker, a separate container for a database is always created alongside the Vikunja image. I would like to avoid this, especially since I want to keep the data from my current Vikunja installation (I know there is also an export function, but I can’t manage to get the export sent to me due to insufficient permissions – but that’s another issue).

I have now adjusted the Docker Compose file… created the whole setup under Stack in Portainer, but unfortunately, I always receive an error message:

“Since --detach=false was not specified, tasks will be created in the background. In a future release, --detach=false will become the default. failed to create service vikunja_newer_vikunja: Error response from daemon: rpc error: code = FailedPrecondition desc = service needs ingress network, but no ingress network is present”

This error message probably has nothing to do with my attempt to use the NAS database… still, I can’t get any further.
I know that there is a guide online (How to Install Vikunja on Your Synology NAS – Marius Hosting), but it doesn’t help me either (especially since it is a different approach).

Here is my Dockerfile:

services:
  vikunja:
    image: vikunja/vikunja
    environment:
      VIKUNJA_SERVICE_PUBLICURL: http://xxxxxx
      VIKUNJA_DATABASE_HOST: 192.168.2.58:3307
      VIKUNJA_DATABASE_PASSWORD: xxxxx
      VIKUNJA_DATABASE_TYPE: mysql
      VIKUNJA_DATABASE_USER: vikunja
      VIKUNJA_DATABASE_DATABASE: vikunja
      VIKUNJA_SERVICE_JWTSECRET: <a super secure random secret>
    ports:
      - 3456:3456
    volumes:
      - /volume1/docker/vikunja2/data:/app/vikunja/files