ok -- i think we could also run the tox tests from another container in the same docker-compose, which would simplify the networking at the expense of having to ship the coverage files back to the host
can this go in a requirements.txt
maybe move to the integration image?
pretty sure we can go back to --remove-orphans instead of the stop and rm - the end result was the same
ROOT=$(git rev-parse --show-toplevel) pushd $ROOT/python_modules/dagster-dask/dagster_dask_tests/dask-docker/