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

[5.2.0] Seperate GetSelfPath implementation for Blaze and Bazel #15223

Merged

Conversation

meteorcloudy
Copy link
Member

In Blaze, we keep using "/proc/self/exe", but in Bazel we resolve this symlink
to the actual Bazel binary.

This is essentially a rollback of
d79ec03
only for Bazel, because it solved an issue that rare in Bazel,
but it's preventing users from running Bazel inside a Linux docker container on Apple Silicon machines.

Fixes #15076

Closes #14391

RELNOTES: None
PiperOrigin-RevId: 441198110

In Blaze, we keep using "/proc/self/exe", but in Bazel we resolve this symlink
to the actual Bazel binary.

This is essentially a rollback of
bazelbuild@d79ec03
only for Bazel, because it solved an issue that rare in Bazel,
but it's preventing users from running Bazel inside a Linux docker container on Apple Silicon machines.

Fixes bazelbuild#15076

Closes bazelbuild#14391

RELNOTES: None
PiperOrigin-RevId: 441198110
@meteorcloudy meteorcloudy added this to the 5.2.0 release blockers milestone Apr 12, 2022
@sgowroji sgowroji added the team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website label Apr 13, 2022
@ckolli5 ckolli5 merged commit b840615 into bazelbuild:release-5.2.0 Apr 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants