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

[GH-ISSUE #68] Default sqlite DB location is not included in a Docker volume #5924

New Issue
Closed
opened 2026-04-20 16:22:45 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-20 16:22:45 -05:00
Owner
Copy Link

Originally created by @eanmclaughlin on GitHub (Mar 2, 2023).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/68

Description

The sqlite DB default location is ./vikunja.db (ie /app/vikunja/vikunja.db in the container).

The Docker configuration section of the docs indicates the only volume required for persistent data is to be mounted at /app/vikunja/files.

None of the sections of the full Docker example page are for an sqlite-based deployment.

Because of all of this, the example configurations and docs do not include the sqlite db file in any persistent storage, resulting in complete loss of user and task data when the container is restarted (I've now lost all my data twice because of this).

Possible fixes:

  • Update the Docker docs to include sections showing sqlite-based deployment configurations, with a new required volume mapped to the sqlite db file location.
  • Update the default location of the sqlite db file to be inside the /app/vikunja/files directory, which is already mapped to a volume in all current Docker examples.

Vikunja Frontend Version

v0.20.3

Vikunja API Version

v0.20.2

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @eanmclaughlin on GitHub (Mar 2, 2023). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/68 ### Description The [sqlite DB default location](https://vikunja.io/docs/config-options/#path) is `./vikunja.db` (ie `/app/vikunja/vikunja.db` in the container). The [Docker configuration section of the docs](https://vikunja.io/docs/install-backend/#docker) indicates the only volume required for persistent data is to be mounted at `/app/vikunja/files`. None of the sections of the [full Docker example page](https://vikunja.io/docs/full-docker-example/) are for an sqlite-based deployment. Because of all of this, the example configurations and docs do not include the sqlite db file in any persistent storage, resulting in complete loss of user and task data when the container is restarted (I've now lost all my data _twice_ because of this). Possible fixes: - Update the Docker docs to include sections showing sqlite-based deployment configurations, with a new required volume mapped to the sqlite db file location. - Update the default location of the sqlite db file to be inside the `/app/vikunja/files` directory, which is already mapped to a volume in all current Docker examples. ### Vikunja Frontend Version v0.20.3 ### Vikunja API Version v0.20.2 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-04-20 16:22:47 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 2, 2023):

I think improving the docs is the way to go as most people won't use the docker image with sqlite and thus an extra volume would be unused in most of the cases.

Do you want to send a PR?

<!-- gh-comment-id:1452463001 --> @kolaente commented on GitHub (Mar 2, 2023): I think improving the docs is the way to go as most people won't use the docker image with sqlite and thus an extra volume would be unused in most of the cases. Do you want to send a PR?
GiteaMirror commented 2026-04-20 16:22:48 -05:00
Author
Owner
Copy Link

@eanmclaughlin commented on GitHub (Mar 2, 2023):

To be clear, the suggested new volume would only be for sqlite-based deployments.

Additionally, setting the default location of the sqlite db to be inside /app/vikunja/files would ensure things Just Work by default with the current docker configuration guidelines. Would not be an issue for existing sqlite deployments as those already either lose all data on restart or have non-default configuration.

I'm kind of surprised you think most won't use sqlite as this seems a great use case (at least for a single user deployment). I might be an outlier since I tend to want to minimize the number of containers I'm running, and I create and manage them via podman/shell scripts/generated systemd units rather than daemonized docker with compose files.

I'll go take a look at editing the docs to at least add some notes about sqlite docker deployments.

<!-- gh-comment-id:1452495447 --> @eanmclaughlin commented on GitHub (Mar 2, 2023): To be clear, the suggested new volume would only be for sqlite-based deployments. Additionally, setting the default location of the sqlite db to be inside `/app/vikunja/files` would ensure things Just Work by default with the current docker configuration guidelines. Would not be an issue for existing sqlite deployments as those already either lose all data on restart or have non-default configuration. I'm kind of surprised you think most won't use sqlite as this seems a great use case (at least for a single user deployment). I might be an outlier since I tend to want to minimize the number of containers I'm running, and I create and manage them via podman/shell scripts/generated systemd units rather than daemonized docker with compose files. I'll go take a look at editing the docs to at least add some notes about sqlite docker deployments.
GiteaMirror commented 2026-04-20 16:22:48 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 3, 2023):

Additionally, setting the default location of the sqlite db to be inside /app/vikunja/files would ensure things Just Work by default with the current docker configuration guidelines. Would not be an issue for existing sqlite deployments as those already either lose all data on restart or have non-default configuration.

This would be a hard breaking change. People might have added a volume to store their sqlite db file, but not the config variable.
It would also affect everyone not using docker and sqlite which is more common than docker + sqlite.

I'm kind of surprised you think most won't use sqlite as this seems a great use case (at least for a single user deployment).

That's probably caused by the ease of spinning up new services with Docker.

I'll go take a look at editing the docs to at least add some notes about sqlite docker deployments.

+1

<!-- gh-comment-id:1453615674 --> @kolaente commented on GitHub (Mar 3, 2023): > Additionally, setting the default location of the sqlite db to be inside /app/vikunja/files would ensure things Just Work by default with the current docker configuration guidelines. Would not be an issue for existing sqlite deployments as those already either lose all data on restart or have non-default configuration. This would be a hard breaking change. People might have added a volume to store their sqlite db file, but not the config variable. It would also affect everyone not using docker and sqlite which is more common than docker + sqlite. > I'm kind of surprised you think most won't use sqlite as this seems a great use case (at least for a single user deployment). That's probably caused by the ease of spinning up new services with Docker. > I'll go take a look at editing the docs to at least add some notes about sqlite docker deployments. +1
GiteaMirror commented 2026-04-20 16:22:49 -05:00
Author
Owner
Copy Link

@tandy-1000 commented on GitHub (Mar 12, 2023):

I look forward to these changes, as I also just bumped into this :)
Could you share your docker config @eanmclaughlin?

<!-- gh-comment-id:1465325960 --> @tandy-1000 commented on GitHub (Mar 12, 2023): I look forward to these changes, as I also just bumped into this :) Could you share your docker config @eanmclaughlin?
GiteaMirror commented 2026-04-20 16:22:49 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 13, 2024):

The docs now properly reflect this - I'm closing this now. Please ping if you have any additional suggestions.

<!-- gh-comment-id:2348367673 --> @kolaente commented on GitHub (Sep 13, 2024): The docs now properly reflect this - I'm closing this now. Please ping if you have any additional suggestions.
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#5924
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?