Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker after update #218

Closed
Palaract opened this issue Apr 20, 2022 · 6 comments
Closed

Docker after update #218

Palaract opened this issue Apr 20, 2022 · 6 comments

Comments

@Palaract
Copy link

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!

@meltyshev
Copy link
Member

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.

@Palaract
Copy link
Author

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!

@loranger
Copy link

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
Copy link

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

@meltyshev
Copy link
Member

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

@immanuelfodor
Copy link

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 up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants