-
Notifications
You must be signed in to change notification settings - Fork 692
Failing to build py3_image due to url_parse #293
Comments
That's a python 3 bug in the google/containerregistry repo: The right solution there is to use |
Ah I see ok, Ill pay attention to updates to this repo and retry the Thanks. |
Is there perhaps a workaround to configure bazel to use python2 when using the container registry? I am having the same issue and tried to pass several flags to bazel, but none of them seem to make this work. The only workaround that I have found so far is to change the symlink from |
If anyone is still having issues with this, I managed to get Bazel to use python2 here by setting I don't know how well supported this environment variable is though. |
@gnatpat Unfortunately that does not work for me |
Any update to this issue? |
We've started migrating https://github.com/google/containerregistry to python3 internally. I can't give any time estimates, but someone is actively working on it now. |
Example workaround with python_path thats working for us:
py3_wrapper.sh:
|
This brings python3 compatibility and should fix bazelbuild#293
* Update containerregistry to v0.0.28 This brings python3 compatibility and should fix #293
Im trying to build python 3 image and it is failing due to:
Is there something Im missing?
Command used to build
ModuleNotFoundError: No module named 'urlparse'
In my
WORKSPACE
i have definedAnd in my
BUILD
file I have the followingError stack trace
The text was updated successfully, but these errors were encountered: