You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bazel shows that it successfully installed, but produces the following error message when running bazel or any other command using bazel: Opening zip "/proc/self/exe": lseek(): Bad file descriptor FATAL: Failed to open '/proc/self/exe' as a zip file: (error: 9): Bad file descriptor
Information
macOS version: Monterey 12.0.1
Intel or Apple chip: Apple M1
Docker version: 4.1.1 (69879)
I have raised this issue with the bazel community, and they said that bazel is supposed to build and that this might have something to do with the way docker emulates x86_64 architectures on ARM chips.
Steps to reproduce the behavior
Start a container for ubuntu x86_64 on an Apple Silicon Mac using --platform linux/amd64
Install bazel using any of the approaches mentioned here.
The text was updated successfully, but these errors were encountered:
Issues go stale after 90 days of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30 days of inactivity.
Prevent issues from auto-closing with an /lifecycle frozen comment.
If this issue is safe to close now please do so.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale
Expected behavior
Should be able to build bazel in Ubuntu.
Actual behavior
Bazel shows that it successfully installed, but produces the following error message when running
bazel
or any other command using bazel:Opening zip "/proc/self/exe": lseek(): Bad file descriptor FATAL: Failed to open '/proc/self/exe' as a zip file: (error: 9): Bad file descriptor
Information
I have raised this issue with the bazel community, and they said that bazel is supposed to build and that this might have something to do with the way docker emulates x86_64 architectures on ARM chips.
Steps to reproduce the behavior
--platform linux/amd64
The text was updated successfully, but these errors were encountered: