* resolved conflict * Docs updated re: Anaconda/certifi issue re #7373 * Removed --console-log "not working" note * A note about Anaconda virtualenvs * Make anaconda comment fit on page * Added README to docker directory * Added install doc reference to master copy of contrib/docker/README.md * merged master, removed mysqlclient * Removed mysql dependency, Anaconda and --console-log references * Add cypress install command to cypress test instructions * Fixed cypress instructions re: port 8081 * Removed anaconda reference, runserver references * Remove anaconda reference * Added back a self-contained version of mysqlclient to dev requirements * Added ASF license to docker README.md |
||
---|---|---|
.. | ||
.env | ||
Dockerfile | ||
README.md | ||
docker-compose.yml | ||
docker-entrypoint.sh | ||
docker-init.sh | ||
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:
SUPERSET_LOAD_EXAMPLES=yes docker-compose run --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)