[Issue]: upgrade from v10.9.3 -> v10.9.6 is has corrupted library.db about jellyfin HOT 5 OPEN

totally get that, and I can/will disable it to get through this. But since this image is from the publisher, as well as the migration that is taking a long time, perhaps that healthcheck endpoint ought to be brought up during a migration to indicate the application is healthy even if it's currently occupied in a migration.

from jellyfin.

Hi, it seems like your issue report has the following item(s) that need to be addressed:

• You have not filled in the environment completely.

This is an automated message, currently under testing. Please file an issue here if you encounter any problems.

from jellyfin.

If you have any kind of timeout mechanisms that will kill a container if the health check fails, please remove that.

Upgrades beyond 10.9.3 requires a db migration that would take some time to finish and if you or your container manager is not patient enough to kill if because the container seems to be "unhealthy", it will kill your db file.

For this exact reason we backup your entire db before doing that. As you can see you have tons of db backups now.

Please use the library.db.bak2 which seems like the first backup before this migration to restore library.db, don't forget to take another backup, then run the container again without all kind of auto-killing feature, be patient to let the migration complete.

from jellyfin.

oh interesting. That HealthCheck is declared by the image publisher

            "Healthcheck": {
                "Test": [
                    "CMD-SHELL",
                    "curl -Lk -fsS \"${HEALTHCHECK_URL}\" || exit 1"
                ],
                "Interval": 30000000000,
                "Timeout": 30000000000,
                "StartPeriod": 10000000000,
                "Retries": 3
            },

from jellyfin.

But the health check itself should not restart your container, it will only indicate that the container is not responding to the health check message.

from jellyfin.