Closed bugsbunny88 closed 2 years ago
Seems like it's not reading the DB file. It could be one of a few things...
its not #1 ; i've done environment variables version with PUIG/PGID to no avail ; its something permissions related at creation because the dailynotes folder is empty even after the container is running . I think the .db file isn't being generated at the onset due to the permission issue .
Try using the tag v1.0-beta10
on docker. That was the version before the permissions.
perfect ; yup I am in now ; works . I will just stick to this tag and keep tabs on this thread for when I can move forward with an update. Atleast I'm up and running ! thanks man
I have also been facing the same issue. While using v1.0-beta10
worked for me, I don't think it has the search option, which would've been quite useful.
Steps to reproduce:
Investigating the logs also showed that while the error is same, the root cause is that the .env
file is not being opened due to a permission error.
I have also tried running as root and passing in PUID
and GUID
for root to no avail.
@bugsbunny88 @kartikay-bagla I reverted the changes for the permissions stuff on the latest docker image. Try it now.
Getting this now.
ERROR: for dailynotes Cannot start service dailynotes: unable to find user abc: no matching entries in passwd file
ERROR: Encountered errors while bringing up the project.
For context here's my docker-compose.yml
version: '3.1'
services:
dailynotes:
image: m0ngr31/dailynotes:latest
restart: unless-stopped
ports:
- '20007:5000'
volumes:
- ./config:/app/config
Good catch. I'm pushing up a fix
Can you ping me once it's uploaded on dockerhub? I'll try it out.
Try now
Works like a charm now!
Thanks for helping out.
I have a bunch of python sqalchemy errors when installing this ; on Docker Synology using portainer ; it was a simple enough guie I was following . stuck at sign up page . [https://mariushosting.com/how-to-install-dailynotes-on-your-synology-nas/]
sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) unable to open database file today at 6:57:58 PM(Background on this error at: https://sqlalche.me/e/14/e3q8)
I have extracted what I feel might be the most relevant code out of the logs ...