github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-22 09:32:36 -05:00
Code Issues 959 Packages Projects Releases 74 Wiki Activity

[GH-ISSUE #1407] The docker image pangolin:postgresql does not check if migrations have already been done #1895

New Issue
Closed
opened 2026-04-16 08:45:12 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-16 08:45:12 -05:00
Owner
Copy Link

Originally created by @kevin-gillet on GitHub (Sep 3, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1407

Originally assigned to: @oschwartz10612, @marcschaeferger on GitHub.

The application starts successfully on the first deployment, but subsequent container restarts fail during the migration phase.

The migration system attempts to recreate existing database tables and re-insert migration version records, resulting in constraint violations.

Configuration of the docker-compose stack :

  pangolin:
    container_name: pangolin
    healthcheck:
      interval: 3s
      retries: 20
      test:
        - CMD
        - curl
        - '-f'
        - http://localhost:3001/api/v1/
    image: fosrl/pangolin:postgresql-1.9.4
    restart: unless-stopped
    volumes:
      - ./pangolin/config:/app/config

This behavior is the same with the following images fosrl/pangolin:postgresql-1.9.[0-3] i tested.

Below are the error logs from a failed container restart:

root@debian-amd64[~]# docker logs 90e12ff1f7d2

> @fosrl/pangolin@0.0.0 start
> DB_TYPE=sqlite NODE_OPTIONS=--enable-source-maps NODE_ENV=development ENVIRONMENT=prod sh -c 'node dist/migrations.mjs && node dist/server.mjs'

Migrations table does not exist, creating it...
Running migrations...
Error running migrations: DrizzleQueryError: Failed query: CREATE TABLE "actions" (
        "actionId" varchar PRIMARY KEY NOT NULL,
        "name" varchar,
        "description" varchar
);

params: 
    at NodePgPreparedQuery.queryWithCache (/app/node_modules/src/pg-core/session.ts:73:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async <anonymous> (/app/node_modules/src/pg-core/dialect.ts:102:7)
    ... 4 lines matching cause stack trace ...
    at async ye (file:///app/dist/migrations.mjs:168:298)
    at async file:///app/dist/migrations.mjs:168:267 {
  query: 'CREATE TABLE "actions" (\n' +
    '\t"actionId" varchar PRIMARY KEY NOT NULL,\n' +
    '\t"name" varchar,\n' +
    '\t"description" varchar\n' +
    ');\n',
  params: [],
  cause: error: relation "actions" already exists
      at /app/node_modules/pg/lib/client.js:545:17
      at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
      at async <anonymous> (/app/node_modules/src/node-postgres/session.ts:149:14)
      at async NodePgPreparedQuery.queryWithCache (/app/node_modules/src/pg-core/session.ts:71:12)
      at async <anonymous> (/app/node_modules/src/pg-core/dialect.ts:102:7)
      at async NodePgSession.transaction (/app/node_modules/src/node-postgres/session.ts:258:19)
      at async PgDialect.migrate (/app/node_modules/src/pg-core/dialect.ts:95:3)
      at async migrate (/app/node_modules/src/node-postgres/migrator.ts:10:2)
      at async Te (file:///app/dist/migrations.mjs:168:695)
      at async ye (file:///app/dist/migrations.mjs:168:298) {
    length: 101,
    severity: 'ERROR',
    code: '42P07',
    detail: undefined,
    hint: undefined,
    position: undefined,
    internalPosition: undefined,
    internalQuery: undefined,
    where: undefined,
    schema: undefined,
    table: undefined,
    column: undefined,
    dataType: undefined,
    constraint: undefined,
    file: 'heap.c',
    line: '1159',
    routine: 'heap_create_with_catalog'
  }
}
Error running migrations: DrizzleQueryError: Failed query: insert into "versionMigrations" ("version", "executedAt") values ($1, $2)
params: 1.9.4,1756942541459
    at NodePgPreparedQuery.queryWithCache (/app/node_modules/src/pg-core/session.ts:73:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async Te (file:///app/dist/migrations.mjs:168:848)
    at async ye (file:///app/dist/migrations.mjs:168:298)
    at async file:///app/dist/migrations.mjs:168:267 {
  query: 'insert into "versionMigrations" ("version", "executedAt") values ($1, $2)',
  params: [ '1.9.4', 1756942541459 ],
  cause: error: duplicate key value violates unique constraint "versionMigrations_pkey"
      at /app/node_modules/pg-pool/index.js:45:11
      at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
      at async <anonymous> (/app/node_modules/src/node-postgres/session.ts:149:14)
      at async NodePgPreparedQuery.queryWithCache (/app/node_modules/src/pg-core/session.ts:71:12)
      at async Te (file:///app/dist/migrations.mjs:168:848)
      at async ye (file:///app/dist/migrations.mjs:168:298)
      at async file:///app/dist/migrations.mjs:168:267 {
    length: 225,
    severity: 'ERROR',
    code: '23505',
    detail: 'Key (version)=(1.9.4) already exists.',
    hint: undefined,
    position: undefined,
    internalPosition: undefined,
    internalQuery: undefined,
    where: undefined,
    schema: 'public',
    table: 'versionMigrations',
    column: undefined,
    dataType: undefined,
    constraint: 'versionMigrations_pkey',
    file: 'nbtinsert.c',
    line: '666',
    routine: '_bt_check_unique'
  }
}

Side note, this is weird to have > DB_TYPE=sqlite on a postgres DB backend image, could it be part of the cause ? I mean the requests seems to be well formed and played, but this is confusing.

Originally created by @kevin-gillet on GitHub (Sep 3, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/1407 Originally assigned to: @oschwartz10612, @marcschaeferger on GitHub. The application starts successfully on the first deployment, but subsequent container restarts fail during the migration phase. The migration system attempts to recreate existing database tables and re-insert migration version records, resulting in constraint violations. Configuration of the docker-compose stack : ``` pangolin: container_name: pangolin healthcheck: interval: 3s retries: 20 test: - CMD - curl - '-f' - http://localhost:3001/api/v1/ image: fosrl/pangolin:postgresql-1.9.4 restart: unless-stopped volumes: - ./pangolin/config:/app/config ``` This behavior is the same with the following images fosrl/pangolin:postgresql-1.9.[0-3] i tested. Below are the error logs from a failed container restart: ``` root@debian-amd64[~]# docker logs 90e12ff1f7d2 > @fosrl/pangolin@0.0.0 start > DB_TYPE=sqlite NODE_OPTIONS=--enable-source-maps NODE_ENV=development ENVIRONMENT=prod sh -c 'node dist/migrations.mjs && node dist/server.mjs' Migrations table does not exist, creating it... Running migrations... Error running migrations: DrizzleQueryError: Failed query: CREATE TABLE "actions" ( "actionId" varchar PRIMARY KEY NOT NULL, "name" varchar, "description" varchar ); params: at NodePgPreparedQuery.queryWithCache (/app/node_modules/src/pg-core/session.ts:73:11) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async <anonymous> (/app/node_modules/src/pg-core/dialect.ts:102:7) ... 4 lines matching cause stack trace ... at async ye (file:///app/dist/migrations.mjs:168:298) at async file:///app/dist/migrations.mjs:168:267 { query: 'CREATE TABLE "actions" (\n' + '\t"actionId" varchar PRIMARY KEY NOT NULL,\n' + '\t"name" varchar,\n' + '\t"description" varchar\n' + ');\n', params: [], cause: error: relation "actions" already exists at /app/node_modules/pg/lib/client.js:545:17 at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async <anonymous> (/app/node_modules/src/node-postgres/session.ts:149:14) at async NodePgPreparedQuery.queryWithCache (/app/node_modules/src/pg-core/session.ts:71:12) at async <anonymous> (/app/node_modules/src/pg-core/dialect.ts:102:7) at async NodePgSession.transaction (/app/node_modules/src/node-postgres/session.ts:258:19) at async PgDialect.migrate (/app/node_modules/src/pg-core/dialect.ts:95:3) at async migrate (/app/node_modules/src/node-postgres/migrator.ts:10:2) at async Te (file:///app/dist/migrations.mjs:168:695) at async ye (file:///app/dist/migrations.mjs:168:298) { length: 101, severity: 'ERROR', code: '42P07', detail: undefined, hint: undefined, position: undefined, internalPosition: undefined, internalQuery: undefined, where: undefined, schema: undefined, table: undefined, column: undefined, dataType: undefined, constraint: undefined, file: 'heap.c', line: '1159', routine: 'heap_create_with_catalog' } } Error running migrations: DrizzleQueryError: Failed query: insert into "versionMigrations" ("version", "executedAt") values ($1, $2) params: 1.9.4,1756942541459 at NodePgPreparedQuery.queryWithCache (/app/node_modules/src/pg-core/session.ts:73:11) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async Te (file:///app/dist/migrations.mjs:168:848) at async ye (file:///app/dist/migrations.mjs:168:298) at async file:///app/dist/migrations.mjs:168:267 { query: 'insert into "versionMigrations" ("version", "executedAt") values ($1, $2)', params: [ '1.9.4', 1756942541459 ], cause: error: duplicate key value violates unique constraint "versionMigrations_pkey" at /app/node_modules/pg-pool/index.js:45:11 at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async <anonymous> (/app/node_modules/src/node-postgres/session.ts:149:14) at async NodePgPreparedQuery.queryWithCache (/app/node_modules/src/pg-core/session.ts:71:12) at async Te (file:///app/dist/migrations.mjs:168:848) at async ye (file:///app/dist/migrations.mjs:168:298) at async file:///app/dist/migrations.mjs:168:267 { length: 225, severity: 'ERROR', code: '23505', detail: 'Key (version)=(1.9.4) already exists.', hint: undefined, position: undefined, internalPosition: undefined, internalQuery: undefined, where: undefined, schema: 'public', table: 'versionMigrations', column: undefined, dataType: undefined, constraint: 'versionMigrations_pkey', file: 'nbtinsert.c', line: '666', routine: '_bt_check_unique' } } ``` Side note, this is weird to have `> DB_TYPE=sqlite` on a postgres DB backend image, could it be part of the cause ? I mean the requests seems to be well formed and played, but this is confusing.
GiteaMirror added the potential bug label 2026-04-16 08:45:12 -05:00
GiteaMirror commented 2026-04-16 08:45:13 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 18, 2025):

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

<!-- gh-comment-id:3304952004 --> @github-actions[bot] commented on GitHub (Sep 18, 2025): This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
GiteaMirror commented 2026-04-16 08:45:13 -05:00
Author
Owner
Copy Link

@marcschaeferger commented on GitHub (Sep 18, 2025):

I'll take a look

<!-- gh-comment-id:3308815033 --> @marcschaeferger commented on GitHub (Sep 18, 2025): I'll take a look
GiteaMirror commented 2026-04-16 08:45:14 -05:00
Author
Owner
Copy Link

@miloschwartz commented on GitHub (Sep 28, 2025):

@kevin-gillet I was unable to reproduce this on latest. I tried on a fresh db, restarted it multiple times, upgraded versions incrementally, and restarted again a few times. Are you still experiencing this problem?

<!-- gh-comment-id:3344291386 --> @miloschwartz commented on GitHub (Sep 28, 2025): @kevin-gillet I was unable to reproduce this on latest. I tried on a fresh db, restarted it multiple times, upgraded versions incrementally, and restarted again a few times. Are you still experiencing this problem?
GiteaMirror commented 2026-04-16 08:45:14 -05:00
Author
Owner
Copy Link

@kevin-gillet commented on GitHub (Sep 30, 2025):

I am not experiencing this on the latest versions (1.10.x), i can restart my instance without any migrations issues now.

<!-- gh-comment-id:3350689239 --> @kevin-gillet commented on GitHub (Sep 30, 2025): I am not experiencing this on the latest versions (1.10.x), i can restart my instance without any migrations issues now.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label potential bug
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/pangolin#1895
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?