Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: unable to open database file

See original GitHub issue

I did the following:

git clone git@github.com:cookiecutter-flask/cookiecutter-flask.git
/cookiecutter-docker.sh
...
cd app
docker-compose up flask-dev

I opened up the site at localhost:5000 and filled out the registration form. Upon submitting it I got the following error:

sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) unable to open database file
(Background on this error at: http://sqlalche.me/e/e3q8)

There was a dev.db/ folder in the app directory owned by root. This seemed strange …

I’m on Manjaro (Arch) Linux. Docker version: Docker version 19.03.4-ce, build 9013bf583a Docker-compose version: docker-compose version 1.24.1, build unknown

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:6

Top GitHub Comments

4reactions

yurivanmiddencommented, Dec 13, 2019

There was a dev.db/ folder in the app directory owned by root. This seemed strange …

True, docker-compose does that when you run docker-compose [ up | run ], as it tries to mount that directory in the container. Run $ touch dev.db before running the containers to create a dev.db file instead of a directory.

3reactions

jamescurtincommented, Mar 17, 2020

Hi, I ran into a similar problem, but touching dev.db didn’t solve the problem for me. Identical stack trace. shrugs

Late response, but one clarification: If a directory named dev.db already exists, touching it won’t have any effect. If you’ve already run into this issue, you need to delete the directory before running touch dev.db (which ensures it exists as a file, not a directory).