Superset is unable to open database file about docker-superset

[amancevice]

The examples are not really meant to be used in a production setting, but more of a reference. I would recommend trying to understand what they are doing a bit more before copy-pasting them into a new location.

Additionally I would recommend against using SQLite as your backend as opposed to a more robust RDB like Postgres or MySQL, but that is up to you.

The configuration of the SQLite example mounts the superset directory to /etc/superset inside the container and the SQLite db file should be found at /etc/superset/superset.db if the container is unable to read/write to that location you will get the error above.

I would exec into the container, cd to /etc/superset and try to determine why the location is not accessible to the superset user.

[prcastro]

That's what I did. I found that the directory's permissions were wrong, so I set that using chmod a+rwx superset from the host and the problem was solved.

Is there any other way of setting these permissions without messing with the permissions outside the container?

[amancevice]

A couple of options off the top of my head:

1. You could stop mounting anything into the container and just use the defaults. This is bad because you'll lose everything when the container is removed.
2. You could create a docker volume and mount that
3. You could use MySQL or Postgres instead of SQLite and avoid the whole thing.