ImSkully

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.

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]

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.

Could you please share the result of the docker create command when you try create the container from this template? Also what Unraid version?

Thanks for notifying! I've updated the description in the template to correctly reflect this as KB instead of MB.

Sorry for the delay, I've bumped the template to use the latest stable version 15.0.2.

@SteelTitan This appears to be an application error caused by Zipline rather than this template, there is an open issue on this here: https://github.com/diced/zipline/issues/582

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

Thanks for reporting, it seems OpenProject are just checking for the presence of the variable regardless of its value.

Updating from v13.0 to v14.1.0 There are some breaking changes introduced between these versions, please refer to the changelog in 14.0.0 and 14.1.0 for anything that may be relevant to you before updating. A notable breaking change for those who require direct access to the built-in Postgres database that also runs in the container:

Sorry for the delay! The docker registry has been moved to openproject/openproject and updated to the latest recommended stable release version 14.1.0. Please try update to the latest version and see if the still issue persists.

@JOKER357thomas Hey, what specific functionality are you trying to enable/configure here? If you can forward the relevant section of OpenProject's documentation that you are trying to follow then I can take a look and see how you can reflect this change on the template, there is no "docker-compose.yml" file for Unraid but rather the template itself that you can modify with variables to achieve the same thing.

Unfortunately yes, this container comes straight from the latest release on the official GitHub: ghcr.io/diced/zipline:latest Zipline is incredibly bulky for some reason.

✨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.

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.

Hey, I have just tested by creating a new container using this template and adjusting just the server IP and key as you mentioned - the container started correctly and created the PG database & migrations. Are you able to provide the full logs? Looking at the screenshot you provided my best guess is that it's something related to the appdata directory it's trying to use (by default is /mnt/user/appdata/openproject/pgdata) which is where it stores the postgres data. Is the directory being created? does the container have permission to it? Are you running low on disk space perhaps?

I haven't used OpenProject via tunnel or proxy so I can't be of much help, though I know you may also have to set SERVER_PROTOCOL_FORCE_HTTPS=true for it to work.

Stumbled into this just now and it was in fact due to the "Allow host to Custom Networks" docker setting being disabled after an unclean shutdown, even though it displays as being enabled.

+1 specifically for optional variables, creating advanced templates with more configurable optional variables is currently not possible.

For anyone who stumbles upon this in the future, this has actually since been made possible by providing a list of values separated by a vertical bar ("|") in the default values field. For instance: Result:

Yeah I've discovered this too (see my last comment) and have removed the variable entirely from the template. It's annoying that OpenProject aren't validating env variables to check they have a value first before using them 🙄 I'll either open a feature request for Unraid to add the ability to make template variables not be added to the container unless they have a value, or open a bug report with OpenProject to validate this variable before using it. Update: Opened a bug report on this and it has since been fixed with OpenProject and will be made available in the next patch release.

@SpuriousIndices Glad you got it it resolved and thanks for sharing - sorry about the DATABASE_URL variable, it seems that OpenProject is not checking to see if the variable value is blank so it will always attempts to use it instead of creating its own Postgres database. I have removed the variable from the template, if anyone is looking to use an existing Postgres database please see 'Using an Existing Postgres Database' in the first post.

Thanks for providing the information, I have updated the template to add the DATABASE_URL variable for users who wish to use an existing Postgres database and updated the topic to include information on this setup along with this query. Edit: This has since been removed as it prevents the container from ever using its own internal database even when left blank. (See comment)

As denoted by the many comments on this thread, the template is not functional out of the box and lacks clear instructions on how to set it up to get running. Your template is very clearly missing the essential variables which has been pointed out already by others (@The_Holocron outlined it very clearly) and you stating we can contribute to your template clearly denotes your reliance on the community rather than maintaining it yourself, which is why I made an improved template with all of the essential variables and clear setup instructions so users can have the container up and running within minutes instead of having to consult this support thread, which on its own provides little to no help to users as displayed by the number of comments from many users having difficulty getting this template to work for over a year which you have seemingly ignored, you only finally commented when the quality of your template was brought into question. If you no longer want to/can't maintain your template that's fine, but don't expect others to make PRs for your templates in order to bring them up to a functional state. Your response here is also incorrect, OpenProject can be run locally without a reverse proxy (and this should be the default that the template tailors to since the majority of users are looking for a local setup). It also can in fact be a one-click install, as is the case with my template. You only just updated your template minutes before commenting to the latest container image. Previously you were using community:12 which is not the latest stable tag (as outlined in the dockerhub overview), my template uses community:13 and I plan to actively maintain this for all future stable releases. My goal isn't to hijack your template, but rather to provide an alternative working template with LTS for the benefit of the community. I don't want to burden your support topic with further comments on this so you are welcome to forum PM me to discuss this further if you wish 🤞 Thanks.

Common Issues Login Credentials Not Working If the default username and password of 'admin' are not working on a fresh install, you have likely previously installed OpenProject and have your old Postgres database data still in your configured Postgres Data Directory (by default this is /mnt/user/appdata/openproject/pgdata) To fix this, delete the contents of this directory with the container stopped and then start it up again - this should recreate a fresh database for you to use with the default credentials. SSL/HTTPS Error on WebUI (ERR_SSL_PROTOCOL_ERROR) If you enabled the OPENPROJECT_HTTPS setting and started the container, you are expected to additionally configure your OpenProject instance such as the hostname and support for running behind a reverse proxy if you are using one; refer to the official documentation on how to do this correctly. Alternatively if you do not have HTTPS enabled and still see this error, it is likely that you have a cached DNS entry which is pointing your current hostname to HTTPS. To resolve this you can simply clear your DNS and wait, or change the WebUI port to something else and restart the container. Updating from v13.0 to >= v14.1.0 See comment below for more information.