Restore fails ("cannot drop table spatial_ref_sys") #2528

Closed
opened 2026-03-22 14:10:40 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @winkelement on GitHub (Feb 10, 2026).

Pre-submission checklist

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

Description

Trying to restore a dump results in an error:

docker exec -i vikunja-app ./vikunja restore --preserve-config files/vikunja-dump_2026-02-10_09-09-28.zip
2026/02/10 10:52:32 failed to create modcache index dir: mkdir /.cache: permission denied
time=2026-02-10T10:52:32.220Z level=INFO msg="Using config file: /etc/vikunja/config.yml"
time=2026-02-10T10:52:32.221Z level=INFO msg="Running migrations…"
time=2026-02-10T10:52:32.239Z level=INFO msg="Ran all migrations successfully."
time=2026-02-10T10:52:32.316Z level=WARN msg="Restoring a dump will wipe your current installation!"
time=2026-02-10T10:52:32.316Z level=WARN msg="To confirm, please type 'Yes, I understand' and confirm with enter:"
Yes, I understand
time=2026-02-10T10:52:42.067Z level=WARN msg="Preserving existing configuration (--preserve-config flag used)"
time=2026-02-10T10:52:42.067Z level=WARN msg="Configuration preserved - ensure your current config is compatible with the restored data"
time=2026-02-10T10:52:42.067Z level=INFO msg=Restoring...
time=2026-02-10T10:52:42.068Z level=INFO msg="Using config file: /etc/vikunja/config.yml"
time=2026-02-10T10:52:42.182Z level=ERROR msg="could not wipe database: pq: cannot drop table spatial_ref_sys because extension postgis requires it"
  • Vikunja Version is 1.0 (both export and import instance)
  • Using paradedb/paradedb:latest for database

Vikunja Version

1.0

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @winkelement on GitHub (Feb 10, 2026). ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description Trying to restore a dump results in an error: ```bash docker exec -i vikunja-app ./vikunja restore --preserve-config files/vikunja-dump_2026-02-10_09-09-28.zip 2026/02/10 10:52:32 failed to create modcache index dir: mkdir /.cache: permission denied time=2026-02-10T10:52:32.220Z level=INFO msg="Using config file: /etc/vikunja/config.yml" time=2026-02-10T10:52:32.221Z level=INFO msg="Running migrations…" time=2026-02-10T10:52:32.239Z level=INFO msg="Ran all migrations successfully." time=2026-02-10T10:52:32.316Z level=WARN msg="Restoring a dump will wipe your current installation!" time=2026-02-10T10:52:32.316Z level=WARN msg="To confirm, please type 'Yes, I understand' and confirm with enter:" Yes, I understand time=2026-02-10T10:52:42.067Z level=WARN msg="Preserving existing configuration (--preserve-config flag used)" time=2026-02-10T10:52:42.067Z level=WARN msg="Configuration preserved - ensure your current config is compatible with the restored data" time=2026-02-10T10:52:42.067Z level=INFO msg=Restoring... time=2026-02-10T10:52:42.068Z level=INFO msg="Using config file: /etc/vikunja/config.yml" time=2026-02-10T10:52:42.182Z level=ERROR msg="could not wipe database: pq: cannot drop table spatial_ref_sys because extension postgis requires it" ``` * Vikunja Version is 1.0 (both export and import instance) * Using `paradedb/paradedb:latest` for database ### Vikunja Version 1.0 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
Author
Owner

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

Did you use the same database for import and export?

@kolaente commented on GitHub (Feb 11, 2026): Did you use the same database for import and export?
Author
Owner

@winkelement commented on GitHub (Feb 12, 2026):

Yes, pulled the latest Image of paradedb/paradedb before export and used the same for import.

@winkelement commented on GitHub (Feb 12, 2026): Yes, pulled the latest Image of `paradedb/paradedb` before export and used the same for import.
Author
Owner

@vikunja-bot-app[bot] commented on GitHub (Mar 4, 2026):

This issue has been fixed in #2355, please check with the next unstable build (should be ready for deployment in ~30min, also on the demo).

@vikunja-bot-app[bot] commented on GitHub (Mar 4, 2026): This issue has been fixed in #2355, please check with the next unstable build (should be ready for deployment in ~30min, also on [the demo](https://try.vikunja.io)).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2528