Hello guys,

I've installed this wonderful container, but I've one problem with the backup function. When I request a backup in Settings, nothing happens. Looking in the log file I find this error:

time=2026-05-10T23:48:43.658+02:00 level=ERROR msg="Error while handling message 17c3ea30-2348-4b4e-849f-3cad8012204e, reason_poisoned=error creating temp file: open /tmp/vikunja-export-735372097.zip: permission denied, topic_poisoned=user.export.requested, handler_poisoned=user.export.requested.handle.user.data.export, subscriber_poisoned=gochannel.GoChannel, payload={\"user\":{\"id\":1,\"name\":\"\",\"username\":\"user\",\"created\":\"2026-05-09T19:48:54Z\",\"updated\":\"2026-05-09T19:51:08Z\"}}"

I don't understand why the container has problems writing to or creating the /tmp folder.

Another problem is that the container doesn't show the ">_ Console" (I'm trying to create a backup of my database with the command "vikunja dump"). If I click in the container's menu, the window closes after a few seconds. It doesn't depend on my browser settings because other containers work.

Thanks in advance.

On 2/4/2025 at 1:42 PM, rocketcoder said:

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!

Hey everyone. If anyone is coming along over a year later like I was, looking at this post and wondering "why would you configure the database file to live inside the container under /etc??" , let me try to explain. Because my autistic ass couldn't figure out why anyone would leave this default value in the template.

It turns out that elsewhere in the template, in the XML but not visible in the parts you can edit, ImSkully has mapped /etc/vikunja/ (inside the container) to /mnt/user/appdata/vikunja/config (on your server.) I was scratching my head over this for a distressingly long time before I noticed that extra volume map. So don't worry, it only looks like you're storing your data in the container - behind the scenes, it has been remapped.

Maybe this was super obvious to most of you out there, but if you were also wondering, I hope this ELI5 helped you figure out just where exactly the db file went!

9 hours ago, Reverend23 said:

Hey everyone. If anyone is coming along over a year later like I was, looking at this post and wondering "why would you configure the database file to live inside the container under /etc??" , let me try to explain. Because my autistic ass couldn't figure out why anyone would leave this default value in the template.

It turns out that elsewhere in the template, in the XML but not visible in the parts you can edit, ImSkully has mapped /etc/vikunja/ (inside the container) to /mnt/user/appdata/vikunja/config (on your server.) I was scratching my head over this for a distressingly long time before I noticed that extra volume map. So don't worry, it only looks like you're storing your data in the container - behind the scenes, it has been remapped.

Maybe this was super obvious to most of you out there, but if you were also wondering, I hope this ELI5 helped you figure out just where exactly the db file went!

Yes, this is correct :) this is how standard Docker mappings work - it's also not hidden as you said, the /etc/vikunja/ mapping is the second entry in the configuration titled Configuration Directory and is always visible to you (not hidden) and this points Vikunja's configuration path to your appdata folder (or any location of your choosing). From there onwards, Vikunja expects all variables such as VIKUNJA_DATABASE_PATH to be relative to the configuration directory path set earlier.

To clarify: within the container, the configuration directory and the SQLite database file is actually still in /etc/vikunja/ which is the correct configuration path as outlined in the official docs; the Docker path mapping to your /mnt/user/appdata/vikunja/config is what sets the real path of where it's stored on your array.