MaxKh

@clunietp No. Also I noticed same errors during "normal" usage (without docker). I had to replace sync logic from **megasimplesync** to self-written python client on top of official MEGA Python...

I have no plans to publish - the sync login is a part of my "private" telegram bot. SDK examples are quite clear and provide good starting point. https://github.com/meganz/sdk/tree/develop/examples/python

Looks like the problem is more complex. Changing provider in `prisma/shema.prisma` to `provider = "sqlite"` causes next error ``` yarn run v1.22.19 $ /data/node_modules/.bin/prisma migrate deploy Prisma schema loaded from...

Nope. I just wrote custom entrypoint script for docker container which replaced the values using `sed` and start "original" CMD `yarn prisma migrate deploy && yarn start`.

> > Nope. I just wrote custom entrypoint script for docker container which replaced the values using `sed` and start "original" CMD `yarn prisma migrate deploy && yarn start`. >...

> now I simply power off the PC entirely, since I got fed up with this. Same here. 560.35.03 and earlier. Archlinux, GeForce RTX 3050 Ti Laptop