-
Notifications
You must be signed in to change notification settings - Fork 3k
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
--no-cache-dir causes AssertionError in wheel.py #6167
Labels
auto-locked
Outdated issues that have been locked by automation
Comments
This comment has been minimized.
This comment has been minimized.
Oops sorry, missed the open one |
It isn't a duplicate of 6166, 6166 does not include the same argument. |
Closing as the underlying issue is same as #6158. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
added
the
auto-locked
Outdated issues that have been locked by automation
label
May 30, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Environment
This issue is caused while building a Dockerfile
Description
A Dockerfile that previously built many times successfully stopped working. I looked into the issue, and pip installing with--no-cache-dir began causing an AssertionError in wheel.py.
Expected behavior
No error
How to Reproduce
Inside Dockerfile, building with the line:
RUN pip install -U --no-cache-dir numpy scipy sklearn pandas Pillow h5py tensorflow-serving-api==1.12.0 boto3 tqdm scikit-image
Output
Exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/pip/_internal/cli/base_command.py", line 176, in main
status = self.run(options, args)
File "/usr/local/lib/python3.5/dist-packages/pip/_internal/commands/install.py", line 346, in run
session=session, autobuilding=True
File "/usr/local/lib/python3.5/dist-packages/pip/_internal/wheel.py", line 848, in build
assert building_is_possible
AssertionError
The text was updated successfully, but these errors were encountered: