harabat commented on issue #9748: URL: https://github.com/apache/superset/issues/9748#issuecomment-1833798497
Still trying to make SQLite work on the official Docker image, if anyone has a solution. I managed to remove the warning by mounting a modified `config.py` with the `PREVENT_UNSAFE_DB_CONNECTIONS = False` setting: ``` shell curl --remote-name https://raw.githubusercontent.com/apache/superset/master/superset/config.py # download config.py file vi config.py # add the line ~PREVENT_UNSAFE_DB_CONNECTIONS = False~ inside the file, before the line containing "WARNING: STOP EDITING HERE" docker run -d -p 8080:8088 -e "SUPERSET_SECRET_KEY=your_secret_key_here" -v /path/to/modified/config.py:/app/superset/config.py # mount local config.py --name superset apache/superset docker exec -it superset superset fab create-admin \ --username admin \ --firstname Superset \ --lastname Admin \ --email [email protected] \ --password admin docker exec -it superset superset db upgrade docker exec -it superset superset init ``` The above removes the SQLite security warning, but trying to connect to the db triggers a `sqlite3.OperationalError` when loading a SQLite db.  I tried to connect with `sqlite:///path/to/my/local.db` and mounting the db into the `/app/` directory and connecting with `sqlite:///local.db`, but keep getting that error. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
