Posted February 12, 20241 yr Vikunja is the to-do application to organize your life. The open-source, self-hostable to-do app - organize everything, on all platforms. Think of Vikunja like the notebook you have with all your things to keep track of. But with superpowers. Website | Registry | Documentation | Template Repo This application template is a single container that runs both the Vikunja API and frontend application in a one-click install with no configuration required to have Vikunja be up and running locally within a matter of seconds, or optionally adjust the configuration settings in the template options to customize your installation. Vikunja Features Stay Organized Organize all of your tasks in projects. Create sub-projects, organize everything hierarchical and keep related stuff grouped together. Collaborate With Peers Vikunja lets you easily share a project with another user or a whole team! Assignments show who's working on what. Use it How You Need It You can view your tasks in the classic list view - or in a Gantt Chart, or Table view, or Kanban Board. Whatever you need! Built For Speed Vikunja is built with speed in mind - every interaction takes less than 100ms. No more loading spinners. Import Tasks From Todoist, Trello or Microsoft To-Do Because work does not happen in one tool only. More information and screenshots can be found on the website. Requirements There are no requirements for this template! Installation & Setup Install Vikunja from community applications (ImSkully's Repository) (Optional) Update template variables as required: Database: By default, the template runs using a SQLite database to store your data in the application directory - to use a separate database engine such as MySQL or Postgres, adjust the VIKUNJA_DATABASE_TYPE variable and other respective database variables with your details. Mailer: The Vikunja Mailer can send emails to users for certain actions such as reminders, to enable this feature set VIKUNJA_MAILER_ENABLED to true and configure the respective mailer variables with your details. Done! Create the container and once it has started, the web UI should be available at the configured port and you will now be able to register and create your account. Additional Configuration There are a number of additional variables available to customize your Vikunja instance, simply edit the container and adjust the existing template variables to your liking. The currently available variables in the configuration is not an exhaustive list of all options, please see the Configuration Options page in Vikunja's documentation for a full list of configuration options available. Support If you have any issues with the template or it has gone out of date, please let me know and I will update it - otherwise you are welcome to leave any support queries below. Edited February 4Feb 4 by ImSkully
February 12, 20241 yr Author ✨Could not connect to db: could not open database file [uid=1000, gid=0]: ... no such file or directory If you encounter the above error when you first attempt to install and start Vikunja using this template before 4th February 2025 (2025-02-04), you are using an outdated version of the template. To resolve this issue: Delete your existing Vikunja container(s) and its application data directory (default is: /mnt/user/appdata/vikunja) Head over to the Community Applications and install Vikunja again as normal The container should now start up without any issues and the WebUI will be accessible at the configured port Prior to this change made on 2025-02-04 to the template, if you started Vikunja it would have created the application data directory for the docker user and group 99:100 however Vikunja itself would be running as user 1000 and no group - this means the container would not have permission to access the files and SQLite database in appdata to function correctly. Existing Vikunja (< v0.23.0) Users If you are an existing user of Vikunja on Unraid (from A75G's repository) running separate containers for the API and frontend application, the new 0.23.0 release of Vikunja combines both applications into a single package (see changelog here for what's new in this version). This template aims to simplify the setup and configuration of Vikunja on Unraid and will automatically update with the latest application changes. To migrate over to this template, you can simply stop your existing containers and install this template as normal and setup the database configuration to that of your previous settings from the vikunja-api container. Once the container has started and you have verified your existing account(s) and data are still present, then the old containers can safely be deleted. Edited February 4Feb 4 by ImSkully
March 17, 20241 yr Does anyone have a working SWAG Config file for vikunja? I currently use this, which ends up in a 502 error: server { listen 443 ssl; listen [::]:443 ssl; server_name vikunja.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for Authelia # include /config/nginx/authelia-server.conf; location / { # enable for Authelia #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app vikunja; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; # root /; # try_files $uri $uri/ /; # index index.html index.htm; } location ~* ^/(api|dav|\.well-known)/ { include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $api_app vikunja-api; set $api_port 3456; set $api_proto http; proxy_pass $api_proto://$api_app:$api_port; client_max_body_size 20M; } } Any help is greatly appreciated, thanks!
July 2, 20241 yr I've updated my Vikunja today and now I can't start the docker due to a permission error. I didn't change anything in my environment, I've just updated the docker image. 2024-07-02T17:57:26.06213419-05:00: INFO ▶ config/InitConfig 001 No config file found, using default or config from environment variables. 2024-07-02T17:57:26.062608159-05:00: CRITICAL ▶ migration/initMigration 002 Could not connect to db: could not open database file [uid=1000, gid=0]: open /etc/vikunja/vikunja.db: permission denied I tried installing Vikunka from scratch on another UnRAID box and got exactly the same error. Any idea of what could be the problem? Edited July 2, 20241 yr by chopeta
July 3, 20241 yr Author 1 hour ago, chopeta said: I've updated my Vikunja today and now I can't start the docker due to a permission error. I didn't change anything in my environment, I've just updated the docker image. <code> 2024-07-02T17:57:26.06213419-05:00: INFO ▶ config/InitConfig 001 No config file found, using default or config from environment variables. 2024-07-02T17:57:26.062608159-05:00: CRITICAL ▶ migration/initMigration 002 Could not connect to db: could not open database file [uid=1000, gid=0]: open /etc/vikunja/vikunja.db: permission denied </code> I tried installing Vikunka from scratch on another UnRAID box and got exactly the same error. Any idea of what could be the problem? Just encountered this myself following the release of Vikunja 0.24.0 earlier today, it seems the PUID & PGID environment variables are not being respected by the Docker container and it will attempt to start with PUID 1000. Hoping Vikunja address this in a fix, though in the meantime you can run the following commands in a terminal to adjust the SQLite database file permissions to user 1000 which the container is attempting to use (replace path to appdata if you have adjusted it from the default): chown -R 1000:1000 /mnt/user/appdata/vikunja chmod -R 770 /mnt/user/appdata/vikunja Edited July 3, 20241 yr by ImSkully
July 3, 20241 yr Thanks for the workaround buddy. I had reverted back to tag 0.23.0 Now I am running 0.24.0 - thanks once again!
August 19, 2024Aug 19 On 3/17/2024 at 12:16 PM, unn4m3d said: Does anyone have a working SWAG Config file for vikunja? I currently use this, which ends up in a 502 error: server { listen 443 ssl; listen [::]:443 ssl; server_name vikunja.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for Authelia # include /config/nginx/authelia-server.conf; location / { # enable for Authelia #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app vikunja; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; # root /; # try_files $uri $uri/ /; # index index.html index.htm; } location ~* ^/(api|dav|\.well-known)/ { include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $api_app vikunja-api; set $api_port 3456; set $api_proto http; proxy_pass $api_proto://$api_app:$api_port; client_max_body_size 20M; } } Any help is greatly appreciated, thanks! I was having some issues after the merger of the frontend + api containers with my reverse proxy setup. Here's what I did to fix it: 1. Change the new container's network to proxynet (the same network my swag container is on) a. This was necessary for the /api/ path to work correctly, otherwise I got a 502 but only on the /api/ path(s) 2. Added my public url in the new container's config (I'm not sure this step was necessary) 3. Updated my swag config file for vikunja (see below) 4. Restarted swag server { listen 443 ssl; listen [::]:443 ssl; server_name vikunja.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for Authelia # include /config/nginx/authelia-server.conf; location / { # enable for Authelia #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app <the unraid ip of the app>; #not the docker ip or docker container name set $upstream_port <the unraid port>; #not the docker port set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } }
October 21, 2024Oct 21 On 7/3/2024 at 3:04 AM, ImSkully said: If you run into "Could not connect to db: could not open database file [uid=1000, gid=0]: open /etc/vikunja/vikunja.db: permission denied" error following the upgrade to Vikunja 0.24+ - there's an easy fix. Add "--user 99:100" flag to Extra Parameters field of the container config (requires Advanced View toggle enabled for the field to appear). The previous versions of Vikunja <0.24 were created with PUID and PGID (99:100) by default, so all files have these permissions. After the uipgrade from earlier versions 0.24+ uses 1000:0 by default, which creates the permission conflict. Reference: https://vikunja.io/docs/full-docker-example/#file-permissions Hope this helps as this seems a more elegant fix than changing ownership and permissions of the files.
January 2Jan 2 On 10/21/2024 at 2:38 PM, yoshiko said: Add "--user 99:100" flag to Extra Parameters field of the container config (requires Advanced View toggle enabled for the field to appear). Thanks for posting this fix; it worked for me. Would like to call out that this error occurred on my first install, no existing db or preferences.
February 4Feb 4 I'm having the "Could not connect to db" issue as well, but none of the above is working for me. This is a fresh install, no prior db.
February 4Feb 4 Author 22 minutes ago, rocketcoder said: I'm having the "Could not connect to db" issue as well, but none of the above is working for me. This is a fresh install, no prior db. Could you please share the result of the docker create command when you try create the container from this template? Also what Unraid version?
February 4Feb 4 Author Can you try set ownership of the appdata directory for Vikunja to user 1000 before starting the container? chown -R 1000 /mnt/cache/appdata/vikunja/* Replace the above path with whatever value you are using for the path defined in 'Application Data Directory' in the docker template. Vikunja stopped supporting the PUID and PGID environment variables a while ago, I will update the template shortly to address this issue. Edited February 4Feb 4 by ImSkully
February 4Feb 4 docker run -d --name='Vikunja' --net='bridge' --pids-limit 2048 -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Blackbox" -e HOST_CONTAINERNAME="Vikunja" -e 'VIKUNJA_SERVICE_ENABLEREGISTRATION'='true' -e 'VIKUNJA_DATABASE_TYPE'='sqlite' -e 'VIKUNJA_DATABASE_PATH'='/mnt/user/appdata/vikunja/vikunja.db' -e 'VIKUNJA_DATABASE_HOST'='' -e 'VIKUNJA_DATABASE_USER'='' -e 'VIKUNJA_DATABASE_PASSWORD'='' -e 'VIKUNJA_DATABASE_DATABASE'='vikunja' -e 'VIKUNJA_MAILER_ENABLED'='false' -e 'VIKUNJA_MAILER_HOST'='' -e 'VIKUNJA_MAILER_PORT'='465' -e 'VIKUNJA_MAILER_AUTHTYPE'='plain' -e 'VIKUNJA_MAILER_USERNAME'='' -e 'VIKUNJA_MAILER_PASSWORD'='' -e 'VIKUNJA_MAILER_SKIPTLSVERIFY'='false' -e 'VIKUNJA_MAILER_FROMEMAIL'='' -e 'VIKUNJA_MAILER_FORCESSL'='false' -e 'VIKUNJA_SERVICE_PUBLICURL'='' -e 'VIKUNJA_SERVICE_ENABLEEMAILREMINDERS'='true' -e 'VIKUNJA_SERVICE_ENABLEUSERDELETION'='true' -e 'VIKUNJA_SERVICE_CUSTOMLOGOURL'='' -e 'VIKUNJA_CORS_ENABLE'='false' -e 'VIKUNJA_CORS_ORIGINS'='' -e 'VIKUNJA_CORS_MAXAGE'='0' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:3456]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/ImSkully/unraid-templates/master/Vikunja/Vikunja.png' -p '3456:3456/tcp' -v '/mnt/user/appdata/vikunja':'/app/vikunja/files':'rw' -v '/mnt/user/appdata/vikunja/config':'/etc/vikunja':'rw' 'vikunja/vikunja:latest' I am on Unraid 7
February 4Feb 4 Author The fix for this has been pushed to the template, please follow the instructions in my updated previous comment here to delete Vikunja and the appdata directory before installing a fresh container again. Alternatively you can simply edit the existing container and add the following to 'Extra Parameters': --user 99:100 @rocketcoder @[email protected]
February 4Feb 4 @ImSkully Thanks for updating. I'm still getting the error even with the corrected permissions. Is there anyway to tell what it is trying to run as?
February 4Feb 4 Author 41 minutes ago, rocketcoder said: @ImSkully Thanks for updating. I'm still getting the error even with the corrected permissions. Is there anyway to tell what it is trying to run as? Actually, the error you're seeing now doesn't appear to be a permission issue but rather the vikunja.db file is missing so I suspect it's trying to locate an existing one instead of creating it; try a fresh install. Edited February 4Feb 4 by ImSkully
February 4Feb 4 I found my issue. I thought this meant the location on the Unraid server itself, not the location from inside the container. Thanks for your help!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.