docs: details on configuring Docker Compose setup #13961
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added details on configuring Docker Compose. Closes #13957
Also updated some things I noticed on the way (e.g. Windows WSL + Docker, the
latest
tag doesn't have thedocker-compose-non-dev.yml
in the same place, the next page is not about connecting a DB driver)I also have a potential other section to add, which I've included here for discussion (it's more a WIP, and I don't know how much is useful/should be on the main installation page):
Debugging Docker Compose
If you don't make any changes to the configuration described above, you shouldn't run into any issues.
However, if you are tweaking the setup,
docker-compose down -v
will remove the volumes associated with the Superset containers.You can choose whether to do this
service_name.pid
file somewhere so the service errors saying it's running)Docker-compose has sometimes treated volumes marked
external
differently, so you may need to investigate whether they are actually removed.