🐛 Bug Report: Not starting after update to v1.6.0 #138

New Issue

OVERLORD · 2025-10-07T00:03:08+03:00

OVERLORD commented

2025-10-07 00:03:08 +03:00

Originally created by @PsychotherapistSam on GitHub.

Originally assigned to: @kmendell on GitHub.

Reproduction steps

After updating to v1.6.0 from v1.5.0 pocket id does not start anymore
Rolling back to v1.5.0 works as expected

Expected behavior

It should start :D

Actual Behavior

See above / logs

Version and Environment

v1.6.0
Docker with this compose file:

services:
  pocket-id:
    image: ghcr.io/pocket-id/pocket-id
    restart: unless-stopped
    env_file: .env
    ports:
      - 3210:1411
    volumes:
      - ./data:/app/data
    healthcheck:
      test: curl -f http://localhost:1411/healthz
      interval: 1m30s
      timeout: 5s
      retries: 2
      start_period: 10s

Log Output

pocket-id-1 | 2025/07/06 18:48:03 failed to run migrations: failed to apply migrations: attempt to write a readonly database (8) in line 0: DELETE FROM schema_migrations
pocket-id-1 exited with code 1
pocket-id-1 | 2025/07/06 18:49:03 failed to run migrations: failed to apply migrations: attempt to write a readonly database (8) in line 0: DELETE FROM schema_migrations
pocket-id-1 exited with code 1
pocket-id-1 | 2025/07/06 18:50:03 failed to run migrations: failed to apply migrations: attempt to write a readonly database (8) in line 0: DELETE FROM schema_migrations
pocket-id-1 exited with code 1

Originally created by @PsychotherapistSam on GitHub. Originally assigned to: @kmendell on GitHub. ### Reproduction steps After updating to v1.6.0 from v1.5.0 pocket id does not start anymore Rolling back to v1.5.0 works as expected ### Expected behavior It should start :D ### Actual Behavior See above / logs ### Version and Environment v1.6.0 Docker with this compose file: ```yaml services: pocket-id: image: ghcr.io/pocket-id/pocket-id restart: unless-stopped env_file: .env ports: - 3210:1411 volumes: - ./data:/app/data healthcheck: test: curl -f http://localhost:1411/healthz interval: 1m30s timeout: 5s retries: 2 start_period: 10s ``` ### Log Output pocket-id-1 | 2025/07/06 18:48:03 failed to run migrations: failed to apply migrations: attempt to write a readonly database (8) in line 0: DELETE FROM schema_migrations pocket-id-1 exited with code 1 pocket-id-1 | 2025/07/06 18:49:03 failed to run migrations: failed to apply migrations: attempt to write a readonly database (8) in line 0: DELETE FROM schema_migrations pocket-id-1 exited with code 1 pocket-id-1 | 2025/07/06 18:50:03 failed to run migrations: failed to apply migrations: attempt to write a readonly database (8) in line 0: DELETE FROM schema_migrations pocket-id-1 exited with code 1

OVERLORD added the bug label 2025-10-07 00:03:08 +03:00

OVERLORD closed this issue

2025-10-07 00:03:09 +03:00

OVERLORD commented

2025-10-07 00:03:11 +03:00

@halictuz commented on GitHub:

same here

failed to run migrations: failed to apply migrations: attempt to write a readonly database (8) in line 0: DELETE FROM schema_migrations

In case somebody isn't aware of it. You can force a version with:

compose.yaml

services:
  pocket-id:
    image: ghcr.io/pocket-id/pocket-id:v1.5.0

and when the latest version v1.6.0 works you can change it to that version.

@halictuz commented on GitHub: same here `failed to run migrations: failed to apply migrations: attempt to write a readonly database (8) in line 0: DELETE FROM schema_migrations` In case somebody isn't aware of it. You can force a version with: compose.yaml ``` services: pocket-id: image: ghcr.io/pocket-id/pocket-id:v1.5.0 ``` and when the latest version v1.6.0 works you can change it to that version.

OVERLORD commented

2025-10-07 00:03:12 +03:00

@jtenniswood commented on GitHub:

yup same, switching tags did fix.

@jtenniswood commented on GitHub: yup same, switching tags did fix.

OVERLORD commented

2025-10-07 00:03:13 +03:00

@KNIF commented on GitHub:

I had the same issue.

This appears to be caused by the new “distroless” image that is also tagged with “latest”:

Changing the tag in the docker-compose to “v1” or to “v1.6” resolved the issue for me.

@KNIF commented on GitHub: I had the same issue. This appears to be caused by the new “distroless” image that is also tagged with “latest”: <img width="536" height="250" alt="Image" src="https://github.com/user-attachments/assets/ebe8b3e7-b215-44f3-831b-2e29fd1e50c6" /> Changing the tag in the docker-compose to “v1” or to “v1.6” resolved the issue for me.

OVERLORD commented

2025-10-07 00:03:14 +03:00

@kmendell commented on GitHub:

This should be fixed now. Let us know if you still are seeing the issue

@kmendell commented on GitHub: This should be fixed now. Let us know if you still are seeing the issue

OVERLORD commented

2025-10-07 00:03:14 +03:00

@mufeedali commented on GitHub:

What do I do to switch to the distroless image?

@mufeedali commented on GitHub: What do I do to switch to the distroless image?

OVERLORD referenced this issue

2025-10-07 00:25:07 +03:00