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

permissions vikunja.db #1932

New Issue
Closed
opened 2026-03-22 13:47:29 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-03-22 13:47:29 -05:00
Owner
Copy Link

Originally created by @jhoogeboom on GitHub (Mar 24, 2024).

Description

Using this docker-compose:

version: '3'

services:
  vikunja:
    image: vikunja/vikunja
    environment:
      VIKUNJA_SERVICE_JWTSECRET: pjicf9Cs8KjNjV
      VIKUNJA_SERVICE_PUBLICURL: http://localhost:3456/
      # Note the default path is /app/vikunja/vikunja.db.
      # This config variable moves it to a different folder so you can use a volume and 
      # store the database file outside the container so state is persisted even if the container is destroyed.
      VIKUNJA_DATABASE_PATH: /db/vikunja.db
    ports:
      - 3456:3456
    volumes:
      - ./files:/app/vikunja/files
      - ./db:/db

I also chown the folders first before starting the docker with:

mkdir $PWD/files $PWD/db
chown 1000 $PWD/files $PWD/db

but I get this error:

vikunja-vikunja-1  | info: creating the new user vikunja with 1000:1000
vikunja-vikunja-1  | usermod: no changes
vikunja-vikunja-1  | 2024-03-20T12:05:51.412579305Z: INFO       ▶ config/InitConfig 001 No config file found, using default or config from environment variables.
vikunja-vikunja-1  | 2024-03-20T12:05:51.413096055Z: CRITICAL   ▶ migration/initMigration 002 Could not connect to db: could not open database file [uid=1000, gid=1000]: open /db/vikunja.db: per

Turns out that the user 1000 does own the folder and the files, but the permission on vikunja.db is zero, I did chmod u+rw db/vikunja.db which fixes it. Perhaps it can be fixed so that the user does not have to do this.

Vikunja Version

latest docker vikunja/vikunja

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Please select

Screenshots

No response

Originally created by @jhoogeboom on GitHub (Mar 24, 2024). ### Description Using this docker-compose: ``` version: '3' services: vikunja: image: vikunja/vikunja environment: VIKUNJA_SERVICE_JWTSECRET: pjicf9Cs8KjNjV VIKUNJA_SERVICE_PUBLICURL: http://localhost:3456/ # Note the default path is /app/vikunja/vikunja.db. # This config variable moves it to a different folder so you can use a volume and # store the database file outside the container so state is persisted even if the container is destroyed. VIKUNJA_DATABASE_PATH: /db/vikunja.db ports: - 3456:3456 volumes: - ./files:/app/vikunja/files - ./db:/db ``` I also chown the folders first before starting the docker with: ``` mkdir $PWD/files $PWD/db chown 1000 $PWD/files $PWD/db ``` but I get this error: ``` vikunja-vikunja-1 | info: creating the new user vikunja with 1000:1000 vikunja-vikunja-1 | usermod: no changes vikunja-vikunja-1 | 2024-03-20T12:05:51.412579305Z: INFO ▶ config/InitConfig 001 No config file found, using default or config from environment variables. vikunja-vikunja-1 | 2024-03-20T12:05:51.413096055Z: CRITICAL ▶ migration/initMigration 002 Could not connect to db: could not open database file [uid=1000, gid=1000]: open /db/vikunja.db: per ``` Turns out that the user 1000 does own the folder and the files, but the permission on vikunja.db is zero, I did `chmod u+rw db/vikunja.db` which fixes it. Perhaps it can be fixed so that the user does not have to do this. ### Vikunja Version latest docker vikunja/vikunja ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Please select ### Screenshots _No response_
GiteaMirror commented 2026-03-22 13:47:30 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 28, 2024):

Can you check if this is still a problem with the unstable build? (do not use your main setup for this)

@kolaente commented on GitHub (Mar 28, 2024): Can you check if this is still a problem with the unstable build? (do not use your main setup for this)
GiteaMirror commented 2026-03-22 13:47:30 -05:00
Author
Owner
Copy Link

@jhoogeboom commented on GitHub (Mar 29, 2024):

Just did a fresh docker compose pull on the vikunja/vikunja:unstable image, deleted the db/files, recreated them with right owner. But the vikunja.db is created without any permissions still:

16777233 20779664 ---------- 1 (1000) (1000) 0 0 "Mar 29 09:44:52 2024" "Mar 29 09:44:52 2024" "Mar 29 09:52:25 2024" "Mar 29 09:44:52 2024" 4096 0 0 db/vikunja.db
@jhoogeboom commented on GitHub (Mar 29, 2024): Just did a fresh docker compose pull on the `vikunja/vikunja:unstable` image, deleted the db/files, recreated them with right owner. But the vikunja.db is created without any permissions still: ``` 16777233 20779664 ---------- 1 (1000) (1000) 0 0 "Mar 29 09:44:52 2024" "Mar 29 09:44:52 2024" "Mar 29 09:52:25 2024" "Mar 29 09:44:52 2024" 4096 0 0 db/vikunja.db ```
GiteaMirror commented 2026-03-22 13:47:30 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 29, 2024):

I was unable to reproduce this with your docker compose file and the latest unstable build.

Maybe this is a filesystem issue? Which OS are you running on? Which FS are you using?

Does it work if you touch and chown the db file manually?

@kolaente commented on GitHub (Mar 29, 2024): I was unable to reproduce this with your docker compose file and the latest unstable build. Maybe this is a filesystem issue? Which OS are you running on? Which FS are you using? Does it work if you `touch` and `chown` the db file manually?
GiteaMirror commented 2026-03-22 13:47:31 -05:00
Author
Owner
Copy Link

@jhoogeboom commented on GitHub (Mar 30, 2024):

Oh it seems a OS issue, I cannot reproduce this on my ubuntu box where my normal setup runs, there the database is created with the right permissions. I thought I'd try out the new container version locally on my laptop which is macOS.

@jhoogeboom commented on GitHub (Mar 30, 2024): Oh it seems a OS issue, I cannot reproduce this on my ubuntu box where my normal setup runs, there the database is created with the right permissions. I thought I'd try out the new container version locally on my laptop which is macOS.
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#1932
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?