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 #2187] The docker docker-compose.yml paradeDB example in the documentation does not work #6583

New Issue
Closed
opened 2026-04-20 17:10:57 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 17:10:57 -05:00
Owner
Copy Link

Originally created by @Vertux on GitHub (Feb 1, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2187

Pre-submission checklist

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

Description

If you use the docker-compose.yml exampe in the documentaion for paradeDB, you will end up with an error.

db-1  | Error: in 18+, these Docker images are configured to store database data in a
db-1  |        format which is compatible with "pg_ctlcluster" (specifically, using
db-1  |        major-version-specific directory names).  This better reflects how
db-1  |        PostgreSQL itself works, and how upgrades are to be performed.
db-1  |
db-1  |        See also https://github.com/docker-library/postgres/pull/1259
db-1  |
db-1  |        Counter to that, there appears to be PostgreSQL data in:
db-1  |          /var/lib/postgresql/data (unused mount/volume)
db-1  |
db-1  |        This is usually the result of upgrading the Docker image without
db-1  |        upgrading the underlying database using "pg_upgrade" (which requires both
db-1  |        versions).
db-1  |
db-1  |        The suggested container configuration for 18+ is to place a single mount
db-1  |        at /var/lib/postgresql which will then place PostgreSQL data in a
db-1  |        subdirectory, allowing usage of "pg_upgrade --link" without mount point
db-1  |        boundary issues.
db-1  |
db-1  |        See https://github.com/docker-library/postgres/issues/37 for a (long)
db-1  |        discussion around this process, and suggestions for how to do so.
Container vikunja-db-1 Error dependency db failed to start
dependency failed to start: container vikunja-db-1 is unhealthy

To make it work, you have to change the volume entry:

volumes:
    - ./db:/var/lib/postgresql/data

to

volumes:
   - ./db:/var/lib/postgresql

Vikunja Version

v1.0.0

Browser and version

Vivaldi 7.8.3925.56 (Offizieller Build) (arm64) - macOS

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @Vertux on GitHub (Feb 1, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2187 ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description If you use the [docker-compose.yml exampe in the documentaion for paradeDB](https://vikunja.io/docs/full-docker-example/#paradedb-full-text-search), you will end up with an error. ``` db-1 | Error: in 18+, these Docker images are configured to store database data in a db-1 | format which is compatible with "pg_ctlcluster" (specifically, using db-1 | major-version-specific directory names). This better reflects how db-1 | PostgreSQL itself works, and how upgrades are to be performed. db-1 | db-1 | See also https://github.com/docker-library/postgres/pull/1259 db-1 | db-1 | Counter to that, there appears to be PostgreSQL data in: db-1 | /var/lib/postgresql/data (unused mount/volume) db-1 | db-1 | This is usually the result of upgrading the Docker image without db-1 | upgrading the underlying database using "pg_upgrade" (which requires both db-1 | versions). db-1 | db-1 | The suggested container configuration for 18+ is to place a single mount db-1 | at /var/lib/postgresql which will then place PostgreSQL data in a db-1 | subdirectory, allowing usage of "pg_upgrade --link" without mount point db-1 | boundary issues. db-1 | db-1 | See https://github.com/docker-library/postgres/issues/37 for a (long) db-1 | discussion around this process, and suggestions for how to do so. Container vikunja-db-1 Error dependency db failed to start dependency failed to start: container vikunja-db-1 is unhealthy ``` To make it work, you have to change the volume entry: ``` volumes: - ./db:/var/lib/postgresql/data ``` to ``` volumes: - ./db:/var/lib/postgresql ``` ### Vikunja Version v1.0.0 ### Browser and version Vivaldi 7.8.3925.56 (Offizieller Build) (arm64) - macOS ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-04-20 17:10:59 -05:00
Author
Owner
Copy Link

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

Now fixed in 82db2cb084

<!-- gh-comment-id:3868367986 --> @kolaente commented on GitHub (Feb 8, 2026): Now fixed in https://github.com/go-vikunja/website/commit/82db2cb084dd3161312e04778a25ed1e845467e0
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#6583
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?