[BUG] Docker starts "successfully" and loops forever when sqlite database is corrupt

[evan]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I had a hard container shutdown (on Unraid) and my sqlite database got corrupted somehow. When the container restarted it started "successfully" but actually was looping this error forever:

2026-02-03 10:38:41 INF syncthing v2.0.14 "Hafnium Hornet" (go1.24.12 linux-amd64) root@buildkitsandbox 2026-02-03 09:33:54 UTC [modernc-sqlite, noupgrade] (log.pkg=main) 2026-02-03 10:38:41 ERR Error opening database (error="openbase (PRAGMA optimize = 0x10002): database disk image is malformed (11)" log.pkg=main)

Expected Behavior

Container should fail to start instead of getting stuck in an error loop.

Steps To Reproduce

1. Install container
2. Corrupt index-v2 sqlite files
3. Restart container

Environment

- Unraid 7.2.3
- Syncthing v2.0.14, Linux (64-bit Intel/AMD Container)  
- Docker installed via Community Applications

CPU architecture

x86-64

Docker creation

Community Application template defaults

Container logs

2026-02-03 10:38:41 INF syncthing v2.0.14 "Hafnium Hornet" (go1.24.12 linux-amd64) root@buildkitsandbox 2026-02-03 09:33:54 UTC [modernc-sqlite, noupgrade] (log.pkg=main)
2026-02-03 10:38:41 ERR Error opening database (error="openbase (PRAGMA optimize = 0x10002): database disk image is malformed (11)" log.pkg=main)

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[the-whiz84]

I have the same issue, same Unraid version and SyncThing version. It just stopped working over the weekend after the Unraid parity check

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[evan]

Issue is still ongoing. If this is the wrong place to report it, let me know.

[aptalca]

If the app fails, the supervisor attempts to restart it.

If you want the container to stop instead, you can probably do it via healthchecks that you can add.

But it's not going to help you in any case if the database is corrupt.

You should restore from a backup

[evan]

Yes, I want the container to stop instead of the supervisor retrying forever.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.