my pangolin container wont start correctly. I do see the following error in the docker logs:
pangolin | > @fosrl/pangolin@0.0.0 start
pangolin | > ENVIRONMENT=prod node dist/migrations.mjs && ENVIRONMENT=prod NODE_ENV=development node --enable-source-maps dist/server.mjs
pangolin |
pangolin | Starting migrations from version 1.18.0
pangolin | Migrations to run:
pangolin | All migrations completed successfully
pangolin | 2026-04-29T07:45:47+00:00 [warn]: Email SMTP configuration is missing. Emails will not be sent.
pangolin | SqliteError: no such column: resources.health
pangolin | at Database.prepare (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21)
pangolin | at BetterSQLiteSession.prepareQuery (/app/node_modules/src/better-sqlite3/session.ts:60:28)
pangolin | at BetterSQLiteSession.prepareOneTimeQuery (/app/node_modules/src/sqlite-core/session.ts:250:15)
pangolin | at SQLiteSelectBase._prepare (/app/node_modules/src/sqlite-core/query-builders/select.ts:916:85)
pangolin | at SQLiteSelectBase.all (/app/node_modules/src/sqlite-core/query-builders/select.ts:950:15)
pangolin | at SQLiteSelectBase.execute (/app/node_modules/src/sqlite-core/query-builders/select.ts:962:15)
pangolin | at SQLiteSelectBase.then (/app/node_modules/src/query-promise.ts:31:15)
pangolin | at process.processTicksAndRejections (node:internal/process/task_queues:104:5) {
pangolin | code: 'SQLITE_ERROR'
pangolin | }
I also tried downgrading to 1.17.1 and do another upgrade to 1.18.0, which showed the same error.
Wenn rolling back to 1.18.0-rc.0 the pangolin instance starts fine.
Environment
OS Type & Version: Ubuntu 24.04.4 LTS
Pangolin Version: 1.18.0
Gerbil Version: 1.3.1
Traefik Version: 3.6.14
Newt Version: 1.12.2
Olm Version: (if applicable)
To Reproduce
Change pangolin version tag in docker-compose.yml from docker.io/fosrl/pangolin:ee-1.18.0-rc.0 to docker.io/fosrl/pangolin:ee-1.18.0
Expected Behavior
The container should start without issues
Originally created by @kesch095 on GitHub (Apr 29, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2925
### Describe the Bug
Hi everyone,
unfortunately, after upgrading from
my pangolin container wont start correctly. I do see the following error in the docker logs:
> pangolin | > @fosrl/pangolin@0.0.0 start
> pangolin | > ENVIRONMENT=prod node dist/migrations.mjs && ENVIRONMENT=prod NODE_ENV=development node --enable-source-maps dist/server.mjs
> pangolin |
> pangolin | Starting migrations from version 1.18.0
> pangolin | Migrations to run:
> pangolin | All migrations completed successfully
> pangolin | 2026-04-29T07:45:47+00:00 [warn]: Email SMTP configuration is missing. Emails will not be sent.
> pangolin | SqliteError: no such column: resources.health
> pangolin | at Database.prepare (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21)
> pangolin | at BetterSQLiteSession.prepareQuery (/app/node_modules/src/better-sqlite3/session.ts:60:28)
> pangolin | at BetterSQLiteSession.prepareOneTimeQuery (/app/node_modules/src/sqlite-core/session.ts:250:15)
> pangolin | at SQLiteSelectBase._prepare (/app/node_modules/src/sqlite-core/query-builders/select.ts:916:85)
> pangolin | at SQLiteSelectBase.all (/app/node_modules/src/sqlite-core/query-builders/select.ts:950:15)
> pangolin | at SQLiteSelectBase.execute (/app/node_modules/src/sqlite-core/query-builders/select.ts:962:15)
> pangolin | at SQLiteSelectBase.then (/app/node_modules/src/query-promise.ts:31:15)
> pangolin | at process.processTicksAndRejections (node:internal/process/task_queues:104:5) {
> pangolin | code: 'SQLITE_ERROR'
> pangolin | }
I also tried downgrading to 1.17.1 and do another upgrade to 1.18.0, which showed the same error.
Wenn rolling back to 1.18.0-rc.0 the pangolin instance starts fine.
### Environment
- OS Type & Version: Ubuntu 24.04.4 LTS
- Pangolin Version: 1.18.0
- Gerbil Version: 1.3.1
- Traefik Version: 3.6.14
- Newt Version: 1.12.2
- Olm Version: (if applicable)
### To Reproduce
- Change pangolin version tag in docker-compose.yml from docker.io/fosrl/pangolin:ee-1.18.0-rc.0 to docker.io/fosrl/pangolin:ee-1.18.0
### Expected Behavior
The container should start without issues
Glad it's not just me, and an issue already created to save me doing it.
And roll back worked for me too. Saved having to revert snapshots
<!-- gh-comment-id:4342521769 -->
@Vyerni commented on GitHub (Apr 29, 2026):
Glad it's not just me, and an issue already created to save me doing it.
And roll back worked for me too. Saved having to revert snapshots
@oschwartz10612 commented on GitHub (Apr 29, 2026):
An update from RC to non RC is not supported. We should probably make this more clear in the release notes apologies. You have to have a clean (not upgraded) database from 1.17 or later to upgrade to 1.18.
Could you try reverting to your 1.17 database that has not been migrated to the RC and then perform the upgrade?
<!-- gh-comment-id:4346131575 -->
@oschwartz10612 commented on GitHub (Apr 29, 2026):
An update from RC to non RC is not supported. We should probably make this more clear in the release notes apologies. You have to have a clean (not upgraded) database from 1.17 or later to upgrade to 1.18.
Could you try reverting to your 1.17 database that has not been migrated to the RC and then perform the upgrade?
However I suspect this is probably gonna affect a few others. And I don't really know you can call it 1.18-rc and 1.18 if they don't play nice with each other?
<!-- gh-comment-id:4347178779 -->
@Vyerni commented on GitHub (Apr 29, 2026):
Yes, I was able to.
However I suspect this is probably gonna affect a few others. And I don't really know you can call it 1.18-rc and 1.18 if they don't play nice with each other?
@AstralDestiny commented on GitHub (Apr 29, 2026):
I mean technically the RC's did say they have breaking changes that could affect non RC and to always backup before moving to it.
<!-- gh-comment-id:4348238879 -->
@AstralDestiny commented on GitHub (Apr 29, 2026):
I mean technically the RC's did say they have breaking changes that could affect non RC and to always backup before moving to it.
I was running 1.18.0.rc.0 and I reverted the DB to a backup in the /conf/db/backup and set the version to a 1.17.1 - then changed to 1.18.0 and it worked perfectly.
Before this I was not aware of the DB backup folder. Hope that helps others!
This is good to know I have not had an issue in the past going from RC to non-RC.
Thank you DEVs!
<!-- gh-comment-id:4348273426 -->
@thesosguy commented on GitHub (Apr 29, 2026):
I was running 1.18.0.rc.0 and I reverted the DB to a backup in the `/conf/db/backup` and set the version to a 1.17.1 - then changed to 1.18.0 and it worked perfectly.
Before this I was not aware of the DB backup folder. Hope that helps others!
This is good to know I have not had an issue in the past going from RC to non-RC.
Thank you DEVs!
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Good to hear! We are calling it out in the rc at the top of the releases in the future to reduce confusion!
<!-- gh-comment-id:4348294392 -->
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Good to hear! We are calling it out in the rc at the top of the releases in the future to reduce confusion!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @kesch095 on GitHub (Apr 29, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2925
Describe the Bug
Hi everyone,
unfortunately, after upgrading from
my pangolin container wont start correctly. I do see the following error in the docker logs:
I also tried downgrading to 1.17.1 and do another upgrade to 1.18.0, which showed the same error.
Wenn rolling back to 1.18.0-rc.0 the pangolin instance starts fine.
Environment
To Reproduce
Expected Behavior
The container should start without issues
@Vyerni commented on GitHub (Apr 29, 2026):
Glad it's not just me, and an issue already created to save me doing it.
And roll back worked for me too. Saved having to revert snapshots
@oschwartz10612 commented on GitHub (Apr 29, 2026):
An update from RC to non RC is not supported. We should probably make this more clear in the release notes apologies. You have to have a clean (not upgraded) database from 1.17 or later to upgrade to 1.18.
Could you try reverting to your 1.17 database that has not been migrated to the RC and then perform the upgrade?
@Vyerni commented on GitHub (Apr 29, 2026):
Yes, I was able to.
However I suspect this is probably gonna affect a few others. And I don't really know you can call it 1.18-rc and 1.18 if they don't play nice with each other?
@AstralDestiny commented on GitHub (Apr 29, 2026):
I mean technically the RC's did say they have breaking changes that could affect non RC and to always backup before moving to it.
@thesosguy commented on GitHub (Apr 29, 2026):
I was running 1.18.0.rc.0 and I reverted the DB to a backup in the
/conf/db/backupand set the version to a 1.17.1 - then changed to 1.18.0 and it worked perfectly.Before this I was not aware of the DB backup folder. Hope that helps others!
This is good to know I have not had an issue in the past going from RC to non-RC.
Thank you DEVs!
@oschwartz10612 commented on GitHub (Apr 29, 2026):
Good to hear! We are calling it out in the rc at the top of the releases in the future to reduce confusion!