mirror of
https://github.com/pocket-id/pocket-id.git
synced 2025-12-06 09:13:19 +03:00
🐛 Bug Report: Unable to update #24
Reference in New Issue
Block a user
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?
Originally created by @mike94100 on GitHub.
Reproduction steps
Attempting to update the container. From 1.6.4 per WebUI to 1.10.
Expected behavior
Update to latest version.
Actual Behavior
Nothing, container eventually starts back up with previous version.
Pocket ID Version
v1.6.4
Database
Default SQLite
OS and Environment
Docker, Debian as VM in Proxmox
Log Output
pocket-id | time=2025-09-15T07:23:31.543Z level=INFO msg="Pocket ID is starting" app=pocket-id version=1.10.0
pocket-id | time=2025-09-15T07:23:31.546Z level=INFO msg="Connected to database" app=pocket-id version=1.10.0 provider=sqlite
pocket-id | time=2025-09-15T07:23:31.546Z level=ERROR msg="Failed to run pocket-id" app=pocket-id version=1.10.0 error="failed to initialize database: failed to run migrations: failed to apply embedded migrations: no migration found for version 20250710011023: read down for version 20250710011023 migrations/sqlite: file does not exist"
@mike94100 commented on GitHub:
Definitely not manually shut down, timing shown is accurate where it shut down a few seconds after I started the container. The only error in the logs was from right above the shutting down entry at the end, copied here:
I also posted in the Discord, here. Copied below:
Will edit this after I can run it on a separate machine.
@stonith404 commented on GitHub:
Were you using any non
latestimage like a development image for testing #544?If so, please try to run the following commands on the database:
Make sure to create a backup of the database first.
@mike94100 commented on GitHub:
I tried to run a completely fresh container & directory with LOG_LEVEL=debug, got the following error:
@mike94100 commented on GitHub:
I only used the v1 tag from the compose example. I have tried setting it to v1.10 as well. I did try those commands, which did not end up working. However, I also tried setting the container to a new created folder which ended up giving me the same problem. I did try pulling the image fresh as well.
Appreciate the help!
For reference, my compose.yaml:
and .env:
And several of the LDAP variables that do end up work successfully.
@stonith404 commented on GitHub:
I don't see any errors in the logs of your comment above. The container appears to be receiving a shutdown signal. This suggests that you either shut down the container manually or something on your system shut it down. Could you try it on another machine? If you didn't shut it down manually, then this might be an issue with your environment.
@stonith404 commented on GitHub:
It looks like the container is using the PR-747 image, which explains the error during the database migration. That image includes a migration that doesn’t exist in the official images, so when the container starts, it can't find the migration you've applied.
To fix this, make sure you’re using an official image such as
latestorv1. Once you switch to an official image, run the commands I shared above and restart the container after that, everything should work as expected.I have no clue why it fails to pull the other images, but it seems that something is broken with your Docker installation. I'm converting this to a discussion because it's not really a bug with Pocket ID itself.