-
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 crashes when running on M1 under qemu #15076
Comments
ckolli5
added
untriaged
team-OSS
Issues for the Bazel OSS team: installation, release processBazel packaging, website
labels
Mar 23, 2022
meteorcloudy
added
type: bug
P2
We'll consider working on this in future. (Assignee optional)
and removed
untriaged
labels
Apr 5, 2022
meteorcloudy
added a commit
that referenced
this issue
Apr 12, 2022
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: 441177762 Change-Id: I48d7283cf7f42f4220e2261f02809c8b5270ef70
meteorcloudy
added a commit
to meteorcloudy/bazel
that referenced
this issue
Apr 12, 2022
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
ckolli5
pushed a commit
that referenced
this issue
Apr 20, 2022
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the problem / feature request:
Bazel fails to self-extract when running under
qemu
since it tries to treat theqemu
binary as a self-extracting archive.Feature requests: what underlying problem are you trying to solve with this feature?
Running Bazel in M1 machines.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Bazel fails to start:
What operating system are you running Bazel on?
macOS
What's the output of
bazel info release
?release 5.0.0
The text was updated successfully, but these errors were encountered: