Closed moookino closed 2 weeks ago
Actually I found a missed copy paste, which I updated in initial message, so it could be used by someone willing to repeat same steps, but I'm still stuck with next step of writing to the DB
yarn run v1.22.19
$ npm-run-all check-db update-tracker start-server
$ node scripts/check-db.js
✓ DATABASE_URL is defined.
✓ Database connection successful.
Error: SQLite database error
attempt to write a readonly database
0: sql_schema_connector::sql_migration_persistence::initialize
with namespaces=None
at schema-engine/connectors/sql-schema-connector/src/sql_migration_persistence.rs:14
1: schema_core::state::ApplyMigrations
at schema-engine/core/src/state.rs:226
✗ Command failed: prisma migrate deploy
Error: SQLite database error
attempt to write a readonly database
0: sql_schema_connector::sql_migration_persistence::initialize
with namespaces=None
at schema-engine/connectors/sql-schema-connector/src/sql_migration_persistence.rs:14
1: schema_core::state::ApplyMigrations
at schema-engine/core/src/state.rs:226
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "check-db" exited with 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Hi @moookino, That was obviously the wrong DATABASE_TYPE for the first error you had. Now it's a permission error, maybe caused by the single database file you have as a volume.
I suggest trying with a whole specific folder:
[...]
environment:
DATABASE_URL: 'file:/umami-db/database.db'
[...]
volumes:
- ./db:/umami-db
I will release a new version, feel free to get back if you are still trying to make it work.
I did figure this part out, but thanks anyway, closing 🙂
Hi @Maxime-J
I'm also trying to adapt Dockerfile to include sqlite, but I'm not sure at which phase I should inject patch from discussion on closed https://github.com/Maxime-J/umami-sqlite/issues/2 builder phase seems to be the right one, but I see mysql db detected instead in the build log message, which is confusing and I end up getting same problem with unable to connect to db Can you help me to find what's wrong, seems like patch as part of builder phase not applied correctly? With more digging and logging I did it seems smth wrong with the final changes in the image
When I try to run it seems there's still mysql part in it
docker-compose.yml
Dockerfile