starred/planka
1
0
Fork 0
mirror of https://github.com/plankanban/planka.git synced 2026-02-24 19:08:59 +03:00
Code Issues 396 Packages Projects Releases 16 Wiki Activity

Docker after update #169

New Issue
Closed
opened 2026-02-04 17:37:28 +03:00 by OVERLORD · 6 comments
OVERLORD commented 2026-02-04 17:37:28 +03:00
Owner
Copy Link

Originally created by @Palaract on GitHub (Apr 20, 2022).

Hello!
I use Docker (newest version) and the meltyshev/planka images.
My problem is, that the page doesn't load after the update. I tried rollbacking to 1.0.0-beta but the error is the same.
The output looks as follows:

debug: :: Wed Apr 20 2022 12:07:37 GMT+0000 (Coordinated Universal Time)
debug: Environment : production
debug: Port        : 1337
debug: -------------------------------------------------------
error: Sending 500 ("Server Error") response: 
 AdapterError: Unexpected error from database adapter: relation "public.project_manager" does not exist
    at fn (/app/api/helpers/project-managers/get-many.js:10:27)
    at wrapper (/app/node_modules/@sailshq/lodash/lib/index.js:3282:19)
    at Deferred.parley.retry [as _handleExec] (/app/node_modules/machine/lib/private/help-build-machine.js:1014:29)
    at Deferred.exec (/app/node_modules/parley/lib/private/Deferred.js:286:10)
    at Deferred.tryCatcher (/app/node_modules/bluebird/js/release/util.js:11:23)
    at ret (eval at makeNodePromisifiedEval (/app/node_modules/bluebird/js/release/promisify.js:184:12), <anonymous>:14:23)
    at Deferred.toPromise (/app/node_modules/parley/lib/private/Deferred.js:572:19)
    at Deferred.then (/app/node_modules/parley/lib/private/Deferred.js:431:22)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

Sadly, I do not know which migrations exactly happened to produce this database error, it would be awesome to get some hints!

Originally created by @Palaract on GitHub (Apr 20, 2022). Hello! I use Docker (newest version) and the meltyshev/planka images. My problem is, that the page doesn't load after the update. I tried rollbacking to 1.0.0-beta but the error is the same. The output looks as follows: ```debug: ------------------------------------------------------- debug: :: Wed Apr 20 2022 12:07:37 GMT+0000 (Coordinated Universal Time) debug: Environment : production debug: Port : 1337 debug: ------------------------------------------------------- error: Sending 500 ("Server Error") response: AdapterError: Unexpected error from database adapter: relation "public.project_manager" does not exist at fn (/app/api/helpers/project-managers/get-many.js:10:27) at wrapper (/app/node_modules/@sailshq/lodash/lib/index.js:3282:19) at Deferred.parley.retry [as _handleExec] (/app/node_modules/machine/lib/private/help-build-machine.js:1014:29) at Deferred.exec (/app/node_modules/parley/lib/private/Deferred.js:286:10) at Deferred.tryCatcher (/app/node_modules/bluebird/js/release/util.js:11:23) at ret (eval at makeNodePromisifiedEval (/app/node_modules/bluebird/js/release/promisify.js:184:12), <anonymous>:14:23) at Deferred.toPromise (/app/node_modules/parley/lib/private/Deferred.js:572:19) at Deferred.then (/app/node_modules/parley/lib/private/Deferred.js:431:22) at processTicksAndRejections (node:internal/process/task_queues:96:5) ``` Sadly, I do not know which migrations exactly happened to produce this database error, it would be awesome to get some hints!
OVERLORD commented 2026-02-04 17:37:38 +03:00
Author
Owner
Copy Link

@meltyshev commented on GitHub (Apr 20, 2022):

Hi!
It looks like you had version 0.1.6 before the update. Unfortunately, the latest version contains a lot of breaking changes and is not compatible with previous versions. To fix this, just change it back to 0.1.6 or use the new one from scratch - it will be supported by us and future migrations will be easy.

@meltyshev commented on GitHub (Apr 20, 2022): Hi! It looks like you had version `0.1.6` before the update. Unfortunately, the latest version contains a lot of breaking changes and is not compatible with previous versions. To fix this, just change it back to `0.1.6` or use the new one from scratch - it will be supported by us and future migrations will be easy.
OVERLORD commented 2026-02-04 17:37:39 +03:00
Author
Owner
Copy Link

@Palaract commented on GitHub (Apr 20, 2022):

You're totally right! I have no idea how I could miss that because I was so sure to have used 1.0.0-beta.
I will start from scratch, this is such a cool project and I'm thanking you for your time!

@Palaract commented on GitHub (Apr 20, 2022): You're totally right! I have no idea how I could miss that because I was so sure to have used 1.0.0-beta. I will start from scratch, this is such a cool project and I'm thanking you for your time!
OVERLORD commented 2026-02-04 17:37:48 +03:00
Author
Owner
Copy Link

@loranger commented on GitHub (Apr 21, 2022):

Hi,

Same issue here.
I've always used image: meltyshev/planka:latest (with watchtower automatically updating my docker images) but the latest update broke.
Is there a way to properly migrate data to the latest version ?

@loranger commented on GitHub (Apr 21, 2022): Hi, Same issue here. I've always used `image: meltyshev/planka:latest` (with watchtower automatically updating my docker images) but the latest update broke. Is there a way to properly migrate data to the latest version ?
OVERLORD commented 2026-02-04 17:37:54 +03:00
Author
Owner
Copy Link

@loranger commented on GitHub (Apr 21, 2022):

I found the @Syndamia post regarding this manual migration. 👍🏻

@loranger commented on GitHub (Apr 21, 2022): I found the @Syndamia [post regarding](https://github.com/plankanban/planka/issues/139#issuecomment-871094096) this manual migration. 👍🏻
OVERLORD commented 2026-02-04 17:38:05 +03:00
Author
Owner
Copy Link

@meltyshev commented on GitHub (Apr 21, 2022):

Totally forgot about this helpful post. I've pinned the issue about update via Docker.

@meltyshev commented on GitHub (Apr 21, 2022): Totally forgot about this helpful post. I've pinned the issue about update via Docker.
OVERLORD commented 2026-02-04 17:38:16 +03:00
Author
Owner
Copy Link

@immanuelfodor commented on GitHub (Apr 21, 2022):

I have Planka v0.1.6 Docker, if I follow the above linked post I can surely get v1.0.0 working?

When I installed Planka originally, I went for v1.0.0-beta with a fresh install but I couldn't get it working, the project list was infinitely loading. So I dropped its database, and reinstalled v0.1.6 from scratch. If I try to upgrade, can I roll back to the v0.1.6 image without any problems? Are the breaking changes backwards-compatible just not forwards-compatible, so we need to do steps to make the new version work but we can go back to the old one?

@immanuelfodor commented on GitHub (Apr 21, 2022): I have Planka v0.1.6 Docker, if I follow the above linked post I can surely get v1.0.0 working? When I installed Planka originally, I went for v1.0.0-beta with a fresh install but I couldn't get it working, the project list was infinitely loading. So I dropped its database, and reinstalled v0.1.6 from scratch. If I try to upgrade, can I roll back to the v0.1.6 image without any problems? Are the breaking changes backwards-compatible just not forwards-compatible, so we need to do steps to make the new version work but we can go back to the old one?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
documentation
documentation
duplicate
enhancement
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#169
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?