522e8015cf
Currently docker entrypoint is a bash script. `docker stop` command (or restart in kubernetes) sends SIGTERM to the container but it isn't catched by gunicorn. So gunicorn can't start graceful shutdown which may lead to killing user's connection and also adds 10s (default value) delay for stopping until docker sends SIGKILL. Using `exec` replaces the shell with the process being opened and signals are propagated correctly. Ref: https://docs.docker.com/engine/reference/commandline/stop/ Ref: https://unix.stackexchange.com/questions/146756/forward-sigterm-to-child-in-bash |
||
|---|---|---|
| .. | ||
| .env | ||
| Dockerfile | ||
| README.md | ||
| docker-compose.yml | ||
| docker-entrypoint.sh | ||
| docker-init.sh | ||
| requirements-extra.txt | ||
| superset_config.py | ||
README.md
Getting Start with Superset using Docker
Docker is an easy way to get stated with Superset.
Initializing Database
To initialize the database with a user and example charts, dashboards and datasets run:
docker-compose run -e SUPERSET_LOAD_EXAMPLES=yes --rm superset ./docker-init.sh
This may take a minute.
Normal Operation
To run the container, simply run:
docker-compose up
After several minutes for superset initialization to finish, you can open a browser and view http://localhost:8088
to start your journey.
Developing
While running, the container server will reload on modification of the superset python and javascript source code. Don't forget to reload the page to take the new frontend into account though.
Production
It is also possible to run Superset in non-development mode: in the docker-compose.yml file remove
the volumes needed for development and change the variable SUPERSET_ENV to production.
Resource Constraints
If you are attempting to build on a Mac and it exits with 137 you need to increase your docker resources. OSX instructions: https://docs.docker.com/docker-for-mac/#advanced (Search for memory)