I've recently upgraded from version 6.12.6 to 6.12.14 and everything is working great except for one docker, "ActualServer"

 

https://github.com/actualbudget/actual-server

 

 

I try to start it, and it just spins for a few seconds and remains stopped when trying to start.

 

This is what the logs for the container look like when it tries to start:

 

 

 

Node.js v18.20.5

/app/node_modules/better-sqlite3/lib/methods/wrappers.js:9
        this[cppdb].exec(sql);
                    ^
SqliteError: no such column: password
    at Database.exec (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:9:14)
    at WrappedDatabase.exec (file:///app/src/db.js:30:20)
    at Migration.up (file:///app/migrations/1718889148000-openid.js:4:24)
    at next (/app/node_modules/migrate/lib/migrate.js:35:45)
    at migrate (/app/node_modules/migrate/lib/migrate.js:76:3)
    at MigrationSet.migrate (/app/node_modules/migrate/lib/set.js:123:3)
    at MigrationSet.up (/app/node_modules/migrate/lib/set.js:107:8)
    at file:///app/src/migrations.js:23:23
    at /app/node_modules/migrate/index.js:62:5
    at /app/node_modules/migrate/lib/load-migrations.js:97:7 {
  code: 'SQLITE_ERROR'
}

Node.js v18.20.5

/app/node_modules/better-sqlite3/lib/methods/wrappers.js:9
        this[cppdb].exec(sql);
                    ^
SqliteError: no such column: password
    at Database.exec (/app/node_modules/better-sqlite3/lib/methods/wrappers.js:9:14)
    at WrappedDatabase.exec (file:///app/src/db.js:30:20)
    at Migration.up (file:///app/migrations/1718889148000-openid.js:4:24)
    at next (/app/node_modules/migrate/lib/migrate.js:35:45)
    at migrate (/app/node_modules/migrate/lib/migrate.js:76:3)
    at MigrationSet.migrate (/app/node_modules/migrate/lib/set.js:123:3)
    at MigrationSet.up (/app/node_modules/migrate/lib/set.js:107:8)
    at file:///app/src/migrations.js:23:23
    at /app/node_modules/migrate/index.js:62:5
    at /app/node_modules/migrate/lib/load-migrations.js:97:7 {
  code: 'SQLITE_ERROR'
}

Node.js v18.20.5
Checking if there are any migrations to run for direction "up"...
Checking if there are any migrations to run for direction "up"...
Checking if there are any migrations to run for direction "up"...

 

 

 

Anyone have any idea what might be causing this?

You can try removing and reinstalling the container from apps, if that doesn't work recommend looking for the container support thread:

 

Getting the same error message.  Container won't start after latest upgrade.  Any help offered from the support thread?

I've had the same issues with ActualServer as well but I've been on 6.12.10 for quite some time so I don't think it's the upgrade of your server that caused your issue. I would notice, it would run fine for a while and I'd notice one day that it just stopped, and this happened multiple times. I'd have to restore from a backup after the crash.

 

After I fixed it to a specific version (in my case: actualbudget/actual-server:24.12.0) it doesn't crash on it's own any longer, so I suspect something breaks from the container itself updating (but I'm mainly still on YNAB so I'm just running Actual to learn/test things out).

 

I went to their github page and in their issues I found this that might help: https://github.com/actualbudget/actual-server/issues/521 

Edited January 11, 20251 yr by God_TM

Hi, please see the pinned thread at my template repo

https://github.com/hofq/docker-templates/issues/29