-
-
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
major version bump of virtualenv (updated 2019-02-10) breaks multistage docker builds using pipenv #4128
Comments
pipenv
I also created an issue in the virtualenv project, #1560 |
What is the short term workaround? Is it possible to set the virtualenv version? Or add |
@dms-cat Sure, you can install as |
I also suffered from this, in my case i have the The virtual environment now depends on the If you copy the |
Sadly |
I got through it with the following in my Dockerfile
|
It seems like adding an environment variable to the
When I use that it produced a virtual environment without any symlinks back to |
Looks like virtualenv 20.0.2 was just released and reverted the |
We are still getting error with the latest version of virtualenv Building wheels for collected packages: distlib |
This appears to be fixed with the latest version of virtualenv |
I experience the same issue. I roll back virtualenv version to |
Issue description
Pipenv installs new version of virtualenv (20.0.1) when updated or installed for the first time.
The new version of virtualenv, which is a complete rewrite and does not have the same virtualenv directory structure as previous major release, appears to break python apps deployed using a multistage docker build process, ie.
Expected result
Running container should result in the executable running successfully.
Actual result
Executable fails with
ModuleNotFoundError: No module named 'pkg_resources'
The text was updated successfully, but these errors were encountered: