Application failed to start: Dirty database version 18.

[smokey007]

Bug description
After updating to the latest version The container runs into an error

I tried a fresh install as well but no luck.

Steps to reproduce
Pulled new image and ran it

Expected behavior
To expose a port.

Screenshots and logs
2025-10-31T01:17:00.705Z INFO Welcome to nginx ignition 2025-10-31T01:17:00.705Z WARN Unable to read configuration properties file: open nginx-ignition.properties: no such file or directory 2025-10-31T01:17:00.716Z INFO Serving frontend files from /opt/nginx-ignition/frontend 2025-10-31T01:17:00.718Z INFO Starting database connection to ignitiondb on db:5432 using username ignitionuser and SSL mode disable 2025-10-31T01:17:00.809Z INFO Running database migrations from /opt/nginx-ignition/migrations/postgres 2025-10-31T01:17:00.812Z FATAL Application failed to start: Dirty database version 18. Fix and force version. dillmann.com.br/nginx-ignition/core/common/log.Fatalf /home/runner/work/nginx-ignition/nginx-ignition/core/common/log/logger.go:41 main.main /home/runner/work/nginx-ignition/nginx-ignition/application/main.go:16 runtime.main /opt/hostedtoolcache/go/1.25.3/x64/src/runtime/proc.go:285

Environment

• OS (e.g. Linux, macOS) Ubuntu
• Execution mode (e.g. Docker, local installation) Docker
• Version (e.g. 2.10.0) 28.5.0

[lucasdillmann]

Hi, @smokey007.

That shouldn't happen. To help me understand what's going on, could you run the following SQL and then send me the log for the first time the application tries to start?

update schema_version set dirty = false, version = 17;

[lucasdillmann]

@smokey007, you can ignore my previous request since I was able to reproduce the error. I'm taking down the latest version for now and working into a fix.

For now, you can still execute the previous SQL and then downgrade to version 2.17.1 or 2.17.0. I will update this issue when the fix is available.

[smokey007]

Thank you for the fix. I look forward to testing the new update when its fixed.

[lucasdillmann]

@smokey007, version 2.18.1 is out with the fix. You don't need to execute the SQL I've mentioned before if you haven't already, the app will do it for you if needed.

Thanks for reporting the bug. Please let me know if you find anything odd.