yeah, I'm guessing at might be that your base system is somehow incompatible with the image I pushed 🤔

Reply to this note

Please Login to reply.

Discussion

It's better, the command `npx prisma db push` can be executed but it doesn't go far more than that, the command get stuck and do nothing (I let it run for 15 minutes) and cancel it

And then got this error on app.nsecbunker.com

```

Failed: Invalid `db_js_1.default.keyUser.count()` invocation in /app/dist/daemon/run.js:47:58 44 const key = { 45 name, 46 npub: user.npub, → 47 userCount: await db_js_1.default.keyUser.count( The table `main.KeyUser` does not exist in the current database.

```

This is what the console print and stay here

```

Prisma schema loaded from prisma/schema.prisma

Datasource "db": SQLite database "nsecbunker.db" at "file:../config/nsecbunker.db"

```

does that file exist inside the container? it should have been generated by running the migrations 🤔

Yes it is

But it seems the path is not the "right" one when using in docker

Trying to modify it now

Okay the file exists prisma/schema.prisma in the container and have some content in it

what about /app/nsecbunker.db?

It's under /app/config/nsecbunker.db

But empty

That’s the right path.

Interesting that it’s empty though!

Can you run npx prisma db push

Let’s see if that does it

Otherwise delete the file and run

npx prisma migrate deploy

Thanks for your help, will let it run longer to see

And delete the file you mean /app/config/nsecbunker.db right ?

Okay, something is weird, with docker only it works well but not with docker compose

Any idea why ?