Description of the problem / feature request:
Problem building Bazel inside a Ubuntu docker container built for an M1 Mac.
Feature requests: what underlying problem are you trying to solve with this feature?
Docker is designed to be as OS and architecture agnostic as possible while building a container so that development environments are as consistent inside a team as possible, but Docker can only take care of so many aspects of it. I want to build a specific version of MediaPipe that was forked by my team, and so requires Bazel 3.7.2 and Tensorflow 1.14.0 to be installed and running correctly in the container.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
- Build a Docker container from Ubuntu 18.04 (tried amd64, x64 as well as arm64/v8)
- Download and install Bazel 3.7.2 using the installer.sh script (this part works for x64 as per confirmation from other team members, fails for arm64/v8 and shows no errors for amd64)
What operating system are you running Bazel on?
Ubuntu docker image running on macOS with M1 processor.
What's the output of bazel info release?
No output. Bazel builds but gives error when trying to use it to run bazel build:
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
Opening zip "/proc/self/exe": lseek(): Bad file descriptor
[FATAL 21:37:43.679 src/main/cpp/archive_utils.cc:51] Failed to open '/proc/self/exe' as a zip file: (error: 9): Bad file descriptor
Have you found anything relevant by searching the web?
Replace these lines with your answer.
Places to look:
I have looked at repos of Docker for Mac, Tensorflow, Bazel and MediaPipe. There are mentions of it here and there but the solutions are very specific to the issues raised by the users. There is no general solution of making bazel work with Docker images made on M1.
Description of the problem / feature request:
Problem building Bazel inside a Ubuntu docker container built for an M1 Mac.
Feature requests: what underlying problem are you trying to solve with this feature?
Docker is designed to be as OS and architecture agnostic as possible while building a container so that development environments are as consistent inside a team as possible, but Docker can only take care of so many aspects of it. I want to build a specific version of MediaPipe that was forked by my team, and so requires Bazel 3.7.2 and Tensorflow 1.14.0 to be installed and running correctly in the container.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
What operating system are you running Bazel on?
Ubuntu docker image running on macOS with M1 processor.
What's the output of
bazel info release?No output. Bazel builds but gives error when trying to use it to run
bazel build:Have you found anything relevant by searching the web?
I have looked at repos of Docker for Mac, Tensorflow, Bazel and MediaPipe. There are mentions of it here and there but the solutions are very specific to the issues raised by the users. There is no general solution of making bazel work with Docker images made on M1.