github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 11:37:49 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #2230] ValidateFileStorage() blocks docker container starting with Postgresql backend. #6606

New Issue
Closed
opened 2026-04-20 17:12:29 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-20 17:12:29 -05:00
Owner
Copy Link

Originally created by @shizunge on GitHub (Feb 13, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2230

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same problem.

Description

I selfhost Vikunja, running it as a docker container, with a Postgresql database.
My instance failed to start after update to the recently release.

I found that it is due to the container does not have write permission to the path checked by ValidateFileStorage() function.

Question: Does Vikunja still need to access the file system when using Postgresql database?

If not, Could we not invoke ValidateFileStorage() when using Postgresql database please.

Vikunja Version

1.1.0

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @shizunge on GitHub (Feb 13, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2230 ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description I selfhost Vikunja, running it as a docker container, with a Postgresql database. My instance failed to start after update to the recently release. I found that it is due to the container does not have write permission to the path checked by ValidateFileStorage() function. Question: Does Vikunja still need to access the file system when using Postgresql database? If not, Could we not invoke ValidateFileStorage() when using Postgresql database please. ### Vikunja Version 1.1.0 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-04-20 17:12:31 -05:00
Author
Owner
Copy Link

@Vincent-641 commented on GitHub (Feb 13, 2026):

I'm also experiencing this issue. Running Vikunja 1.1.0 in Docker with PostgreSQL, and the container fails to start.

level=ERROR msg="Could not init file handler: storage validation failed: failed to create test file at /app/vikunja/files/.vikunja-check-1770996064228602329: open /app/vikunja/files/.vikunja-check-1770996064228602329: permission denied"
<!-- gh-comment-id:3897808576 --> @Vincent-641 commented on GitHub (Feb 13, 2026): I'm also experiencing this issue. Running Vikunja 1.1.0 in Docker with PostgreSQL, and the container fails to start. ``` level=ERROR msg="Could not init file handler: storage validation failed: failed to create test file at /app/vikunja/files/.vikunja-check-1770996064228602329: open /app/vikunja/files/.vikunja-check-1770996064228602329: permission denied" ```
GiteaMirror commented 2026-04-20 17:12:32 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 13, 2026):

File storage is independent of the database used. If the file storage is not writeable, you won't be able to use task attachments, backgrounds, custom user avatars, and exports. Before we integrated that check, people would complain about these features not working when they did not set it up correctly. The explicit check on start surfaces the error to a point in time when people are looking at it.

If you want to run Vikunja without a volume mount, use S3.

<!-- gh-comment-id:3898581969 --> @kolaente commented on GitHub (Feb 13, 2026): File storage is independent of the database used. If the file storage is not writeable, you won't be able to use task attachments, backgrounds, custom user avatars, and exports. Before we integrated that check, people would complain about these features not working when they did not set it up correctly. The explicit check on start surfaces the error to a point in time when people are looking at it. If you want to run Vikunja without a volume mount, use S3.
GiteaMirror commented 2026-04-20 17:12:32 -05:00
Author
Owner
Copy Link

@shizunge commented on GitHub (Feb 19, 2026):

Is it a good idea to make /app/vikunja/files a volume and have the correct premission (set in Dockerfile)

I hope we can start the container easier.

<!-- gh-comment-id:3924671258 --> @shizunge commented on GitHub (Feb 19, 2026): Is it a good idea to make `/app/vikunja/files` a volume and have the correct premission (set in `Dockerfile`) I hope we can start the container easier.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6606
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?