-
Notifications
You must be signed in to change notification settings - Fork 4k
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
[bazel.build] Problem with /install/docker-container #17070
Comments
Note near the bottom of the page, the example is quite dated as well |
Hello @alexeagle, Can you provide the page link which you referring on above comments. Thanks! |
Ah, I didn't include that since it was automatically captured in the bug title by the Report Issue button link. |
https://bazel.build/install/docker-container is the page that has that button. If the process isn't clear, maybe @fweikert could change the buttons to include the domain name in addition to the path? |
Created a separate issue to update the buttons/include more details in the title & description - thanks @alexeagle! |
Fixes : #17070 (comment) PiperOrigin-RevId: 501775830 Change-Id: Id6dc87cf9e91a4692f406d0ba3e8c1e3f77ff307
2-part issue: 1. Doc references l.gcr.io/google/bazel instead of gcr.io/bazel-public/bazel 2. Example at the bottom of the page is outdated I was able to fix the first but would like some help with the second PiperOrigin-RevId: 500919426 Change-Id: I4ed07865a4eb760df07e3e47d5e8e3fe5e9dce1c
Fixes : #17070 (comment) PiperOrigin-RevId: 501775830 Change-Id: Id6dc87cf9e91a4692f406d0ba3e8c1e3f77ff307
This page suggests using an old registry that's stuck in the past
but Yun documented here
bazelbuild/continuous-integration#1060 (comment)
that the correct place for new versions is now gcr.io/bazel-public/bazel
The text was updated successfully, but these errors were encountered: