-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There was an error connecting to the database! unable to open database file #114
Comments
@prochuk Are you running lsio dockerhub diskover ce 2.3.0? |
@shirosaidev Yes, running lsio docker image diskover-web v2.3.0 community edition (ce). Don't have any var related to database, only ES_HOST, ES_PORT and TZ. |
@prochuk please post a message in lsio discord container support. |
The error is coming from '/app/diskover/diskover_db.py' line 45. 'diskover_db.py' gets the DATABASE parameter from '/app/diskover/config_defaults.py'. Out of the box it is set to:
But it should be:
Apparently 'diskover_db.py' is not changed by setting env vars. It only works if you change '/app/diskover/config_defaults.py' in the diskover container. |
@OpenCV-Peter In line 35 to 39 in diskover_db.py looks for DATABASE env var. In lsio diskover docker container start up, it is not set. Either the config_defaults.py file needs to be changed or DATABASE env var set.
|
Hey guys, Thanks @shirosaidev for the info. I fixed the issue by adding the diskover:
image: lscr.io/linuxserver/diskover
container_name: diskover
hostname: diskover
environment:
PUID: 1000
PGID: 1000
TZ: Europe/Paris
ES_HOST: elasticsearch
ES_PORT: 9200
RUN_ON_START: true
DATABASE: /config/diskoverdb.sqlite3
volumes:
# ... |
I was having the same issue and can confirm adding the DATABASE env fixed it. |
Getting error "There was an error connecting to the database! unable to open database file" when try to run crawl
The text was updated successfully, but these errors were encountered: