When running docker locally, it's pretty silly that we have to do
source ~/.virtualenv/rmc/bin/activate, considering it's an isolated
environment by design.
So either we should skip using the virtualenv in docker, or we
should change the docker environment to activate the virtualenv
automatically on boot somehow.
When running docker locally, it's pretty silly that we have to do
source ~/.virtualenv/rmc/bin/activate, considering it's an isolated environment by design.So either we should skip using the virtualenv in docker, or we should change the docker environment to activate the virtualenv automatically on boot somehow.