-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Usage in Docker #63
Comments
this would be a replacement for that workflow |
I see, thank you. Great work on this @kennethreitz! |
Well, pyenv is more than just a virtualenv manager (in fact, that aspect comes only as a plugin). It's real use case is to manage multiple Python versions on a single machine, which seems orthogonal to the use case of pipenv. So I think the question remains if they play nicely together. |
I believe that https://github.com/kennethreitz/pipenv/issues/98, which we're in the midst of debugging, is caused by a |
So, what is the advised workflow in docker ? I have a project using pipenv that requires twisted that cannot be built into my alpine docker. I want to use the provided alpine package |
@stibbons, yes, you can use |
Great ! |
Does subsequent "pipenv run" knows the latest (i also prefere using exactly the same chain of command between travis/docker and manual dev, instead of having to maintain 2 build scripts) ? |
It would be nice if we could set the use of |
Good idea :) I use pipenv like usual in my docker, simply in prepend all command by pipenv run. This forces the use of a virtualenv inside the docker, maybe it is overkill. But I like the idea of the env var :) |
I'm honestly only using Pipenv because I like the |
@clintonb Agreed. I really want to leverage the protection of the |
|
Also as of next release I enabled |
Thanks @techalchemy! |
What's the best workflow to use Pipenv with Docker?
I am trying to accomplish this with a Django project running inside Docker / Docker Compose.
Any tips / suggestions / ideas?
P.S. also, I am using https://github.com/yyuu/pyenv to automatically activate my virtualenvs and manage local Pythons. Does that not work well with this toolchain?
The text was updated successfully, but these errors were encountered: