build(docker): add script to clean up docker environment

[mars-lan]

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable)

[cobolbaby]

You can try the following command:

docker-compose  -p datahub down -v
docker system prune -all --force 

[jplaisted]

LGTM if we want a "real" nuke, but afaik that command also gets rid of images we probably don't need to get rid of, like kafka and Elasticsearch. Up to you if you want to modify the script to delete just the datahub images and volumes.

[jplaisted]

Yeah, testing that command I had to redownload things like neo4j and Elasticsearch, which all took awhile. Can we kill just our images and volumes?

[mars-lan]

Yeah, testing that command I had to redownload things like neo4j and Elasticsearch, which all took awhile. Can we kill just our images and volumes?

Since this is really to nuke everything so the user can start from a complete clean slate to avoid any possible issues, I think it's okay to drop and redownload those images?

[jplaisted]

Since this is really to nuke everything so the user can start from a complete clean slate to avoid any possible issues, I think it's okay to drop and redownload those images?

/shrug in theory they're isolated from the actual volumes, right? Try it yourself; it has to download a few GBs. Not good for time or data caps :)

[mars-lan]

Since this is really to nuke everything so the user can start from a complete clean slate to avoid any possible issues, I think it's okay to drop and redownload those images?

/shrug in theory they're isolated from the actual volumes, right? Try it yourself; it has to download a few GBs. Not good for time or data caps :)

Good point. Use docker-composer rm instead of docker system prune.

[jplaisted]

Thanks!