Unable to build Docker image #413
Labels
bug
Something isn't working
Comments
|
I haven't dug, so this is a guess, but I'm guessing this issue is restricted to Pipenv and the same version of PyYAML would be fine with standard Pip. If so, that's all the more reason to ditch Pipenv, like we've done elsewhere. If we need strict locking, we can use pip-compile from pip-tools, as elsewhere. |
victorlin
added a commit
that referenced
this issue
Aug 14, 2023
The previous setup using Pipenv started failing on `pipenv sync` without any obvious changes on our end¹. Instead of trying to fix the Pipenv setup, I chose to move the dependencies from the Pipfile into a simpler pip install. This lets pip do its own dependency resolution which is sufficient for the needs here. ¹ #413
victorlin
added a commit
that referenced
this issue
Aug 19, 2023
The previous setup using Pipenv started failing on `pipenv sync` without any obvious changes on our end¹. Instead of trying to fix the Pipenv setup, I chose to move the dependencies from the Pipfile into a simpler requirements.txt. This lets pip do its own dependency resolution which is sufficient for the needs here. ¹ #413
victorlin
added a commit
that referenced
this issue
Feb 20, 2024
The previous setup using Pipenv started failing on `pipenv sync` without any obvious changes on our end¹. Instead of trying to fix the Pipenv setup, I chose to move the dependencies from the Pipfile into a simpler requirements.txt. This lets pip do its own dependency resolution which is sufficient for the needs here. ¹ #413
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I ran update-image.yml on
masterand it failed while runningpipenv syncin the Docker build.Others on the internet have reported that this error comes from a version of PyYAML (which is included in the Pipfile.lock).
I tried re-generating the lock file using
pipenv locklocally but it failed.The text was updated successfully, but these errors were encountered: