Skip to content
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

Closed
alexeagle opened this issue Dec 23, 2022 · 5 comments
Closed

[bazel.build] Problem with /install/docker-container #17070

alexeagle opened this issue Dec 23, 2022 · 5 comments
Assignees
Labels
P2 We'll consider working on this in future. (Assignee optional) team-Documentation Documentation improvements that cannot be directly linked to other team labels team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: documentation (cleanup)

Comments

@alexeagle
Copy link
Contributor

This page suggests using an old registry that's stuck in the past

docker run --rm -it l.gcr.io/google/bazel:latest version
Build label: 3.5.0

but Yun documented here
bazelbuild/continuous-integration#1060 (comment)
that the correct place for new versions is now gcr.io/bazel-public/bazel

@alexeagle
Copy link
Contributor Author

Note near the bottom of the page, the example is quite dated as well
Build label: 0.17.1

@sgowroji sgowroji added more data needed team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website labels Dec 23, 2022
@sgowroji
Copy link
Member

Hello @alexeagle, Can you provide the page link which you referring on above comments. Thanks!

@alexeagle
Copy link
Contributor Author

Ah, I didn't include that since it was automatically captured in the bug title by the Report Issue button link.

@alexeagle
Copy link
Contributor Author

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?

@sgowroji sgowroji added type: documentation (cleanup) untriaged team-Documentation Documentation improvements that cannot be directly linked to other team labels and removed more data needed team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website labels Dec 26, 2022
@keertk keertk added P2 We'll consider working on this in future. (Assignee optional) and removed untriaged labels Jan 9, 2023
@keertk keertk self-assigned this Jan 9, 2023
@keertk keertk added the team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website label Jan 9, 2023
@keertk
Copy link
Member

keertk commented Jan 10, 2023

Created a separate issue to update the buttons/include more details in the title & description - thanks @alexeagle!
(We're looking into the original issue in the meantime as well.)

copybara-service bot pushed a commit that referenced this issue Jan 13, 2023
Fixes : #17070 (comment)
PiperOrigin-RevId: 501775830
Change-Id: Id6dc87cf9e91a4692f406d0ba3e8c1e3f77ff307
hvadehra pushed a commit that referenced this issue Feb 14, 2023
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
hvadehra pushed a commit that referenced this issue Feb 14, 2023
Fixes : #17070 (comment)
PiperOrigin-RevId: 501775830
Change-Id: Id6dc87cf9e91a4692f406d0ba3e8c1e3f77ff307
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 We'll consider working on this in future. (Assignee optional) team-Documentation Documentation improvements that cannot be directly linked to other team labels team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: documentation (cleanup)
Projects
None yet
Development

No branches or pull requests

3 participants