Crash after startup in Docker container after attempting migration.

[jacksaturn]

⚠️ Please verify that your question has not already been reported

• I have searched the existing issues and found no similar reports.

🛡️ Security Policy

• I have read and agree to Uptime Kuma's Security Policy.

📝 Describe your problem

I've had Uptime Kuma running in a Docker container inside a Promox VM for a good while now. As I'm attempting to move that container to a VM on another one of my Proxmox nodes, I'm running into a startup problem.

After executing the docker compose up -d command, the logs show a repeated boot loop, specifically the lines of code pasted below. The Docker container reboots continuously, never fully starting up. I've attempted removing my pre-existing data directory and spinning up the container from scratch, but the result is the same.

As far as I can tell, the setup of the VM is the same between the old location and the new one, and nothing has changed in my Docker Compose file, so I'm not sure what is causing this. Any suggestions are appreciated!

📝 Error Message(s) or Log

[uptime-kuma] 2026-05-11T04:32:51.314624305Z node:internal/modules/run_main:92
[uptime-kuma] 2026-05-11T04:32:51.314707757Z   const type = getNearestParentPackageJSONType(mainPath);
[uptime-kuma] 2026-05-11T04:32:51.314713642Z                ^
[uptime-kuma] 2026-05-11T04:32:51.314715873Z 
[uptime-kuma] 2026-05-11T04:32:51.314717610Z Error: Invalid package config /app/package.json.
[uptime-kuma] 2026-05-11T04:32:51.314719415Z     at shouldUseESMLoader (node:internal/modules/run_main:92:16)
[uptime-kuma] 2026-05-11T04:32:51.314721220Z     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:20)
[uptime-kuma] 2026-05-11T04:32:51.314722977Z     at node:internal/main/run_main_module:36:49 {
[uptime-kuma] 2026-05-11T04:32:51.314724642Z   code: 'ERR_INVALID_PACKAGE_CONFIG'
[uptime-kuma] 2026-05-11T04:32:51.314726342Z }
[uptime-kuma] 2026-05-11T04:32:51.314728011Z 
[uptime-kuma] 2026-05-11T04:32:51.314730179Z Node.js v22.22.2

🐻 Uptime-Kuma Version

2.3.2

💻 Operating System and Arch

Ubuntu 24.04.4 LTS (Linux 6.8.0-111-generic)

🌐 Browser

Zen Browser (macOS)

🖥️ Deployment Environment

• Runtime Environment:
  • Docker: Version 29.4.3
  • Docker Compose: Version not specified
  • Portainer (BE/CE): Version 2.39.2 (LTS: Yes)
  • Node.js: Version X.X.X (LTS: Yes/No)
• Database:
  • SQLite: External (local storage)
• Database Storage:
  • Filesystem:
    • Linux: ext4/ZGS
  • Storage Medium: NVME
• Uptime Kuma Setup:
  • Number of monitors: 33

[louislam]

Try to spin up a fresh Uptime Kuma with single docker command in README.md.

If same error => the docker image is corrupted, redownload the image
If not => something is wrong in your compose file

[jacksaturn]

Thank you for this guidance. Before running the command in README.md, I made sure that the prior images I downloaded were deleted along with my docker-compose file, my .env file and my data directories.

I ran the command as
docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:2
but I changed "uptime-kuma" in -v uptime-kuma:/app/data to reflect my local file directory.

The error happened again — JSON errors and repeated restarting.

Is there a reason why I might be inadvertently downloading corrupted images?

As I'm waiting to solve this issue, I'm keeping Uptime Kuma active at its original location, with the same Docker Compose file. In that location, there's no corruption and I can pull the image without any issues.

[louislam]

If you sure a fresh Uptime Kuma also run into the problem, just try to prune everything and pull the image again.

Reference Answer from immich: immich-app/immich#22290 (comment)

I don't know the reason. As far as I know, docker pull will verify the layer files after downloaded. So it did pass the checksum. It should be corrupted afterwards.

It could be a hardware level issue, or very rarely issue - Bit Rot.