Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

Avoid needing to activate virtualenv in Docker #287

Open
jlfwong opened this issue Jun 27, 2016 · 0 comments
Open

Avoid needing to activate virtualenv in Docker #287

jlfwong opened this issue Jun 27, 2016 · 0 comments

Comments

@jlfwong
Copy link
Member

jlfwong commented Jun 27, 2016

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants