-
Notifications
You must be signed in to change notification settings - Fork 578
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
make docker-build-dev fails #624
Comments
/assign |
/lifecycle active |
Looks like this has to do with python versions. Arch's default python is 3.7.2. I don't use bazel so I don't know the "right" way to do that. I just replaced the files in the zip file ( |
Yes, need to have Python 2 as the active |
I had some edits to the developer doc atound how to build an image after
making changes. I’ll see how to include this info as well.
…On Wed, Mar 6, 2019 at 4:43 AM Naadir Jeewa ***@***.***> wrote:
Previous tickets on the same issue: #347
<#347>
and #361
<#361>
Open to suggestions on how to make this clearer to developers.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#624 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AV0ASnO4x2GYwPFoew2EUT0LktJf0mwpks5vT7f_gaJpZM4bf1zG>
.
|
One possibility is to force a virtualenv as part of the Makefile |
Not in favour of forcing virtualenv on people if they have other ways to get Py 2.7 (system. pyenv, Nix, Guix etc...) to work. Rather, google/containerregistry#109 or similar should be merged. |
I've documented this in the development doc till we have the correct fix in place. #639 |
/remove-lifecycle active |
As per google/containerregistry#109 (comment), there is the possibility to resolve this upstream with the current release of Bazel. The Python mismatch issue is real and documented. Think this is more of a priority/long-term as we have a workaround. |
/priority important-longterm |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
we now force to python 2 /close |
@chuckha: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/kind bug
What steps did you take and what happened:
What did you expect to happen:
I expected a container image to be built
Anything else you would like to add:
I'm guessing there's an env variable that should be set? If so, these should be asserted in the makefile before bazel is run.
Environment:
master@13b5457
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: