Upgrade to v2 interrupted by docker healthcheck

[derekoharrow]

📑 I have found this issue...

Attempted upgrade from v1 to v2. The DB upgrade was working fine, but then the container got killed by the in built docker healthcheck.

To get around this for me, I restored by DB/backup and then cleared down all the stats so that the upgrade didn't take too long for the healthcheck.

I guess another alternative would be to temporarily disable the healthcheck before upgrading, or make the healthcheck work during the upgrade process.

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

No response

👟 Reproduction steps

Follow the v2 migration guide without clearing history/shrinking DB first.

👀 Expected behavior

Should upgrade ok

😓 Actual Behavior

Upgrade interrupted by healtcheck timing out.

🐻 Uptime-Kuma Version

2.0.0-beta.0

💻 Operating System and Arch

Ubuntu 22.04.2 LTS

🌐 Browser

n/a

🖥️ Deployment Environment

• Runtime: Docker version 27.3.1, build ce12230
• Database: sqlite/embedded
• Filesystem used to store the database on: ext3
• number of monitors: 80+

📝 Relevant log output

No response

[louislam]

Do you have the last log before healthcheck restarted?

I thought it was fixed by: #5258

[derekoharrow]

Sorry - they've gone. It was progressing with the DB upgrade and then the container was stopped/restarted by the healthcheck by the look of it.

I only pulled the container an hour or two ago. I think I was using the slim rootless one to begin with (until I later realised I needed the rooted one to work with docker).