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
I would like to propose adding support for the ARM64 architecture to the Docker image of the BigQuery emulator. With the increasing popularity and usage of ARM64-based systems, especially with the advent of ARM-based processors in both servers and personal computing devices, it is crucial for the Docker image to be compatible with these architectures.
Adding ARM64 support to the Docker image will:
• Enhance the emulator’s usability on a broader range of hardware.
• Enable developers using ARM64-based systems to leverage the BigQuery emulator Docker image without the need for workarounds or additional virtualization.
• Promote greater flexibility and inclusivity for developers working on various hardware configurations.
I believe this enhancement will greatly benefit the community and align with the ongoing industry trend towards ARM64 adoption. Thank you for considering this request.
The text was updated successfully, but these errors were encountered:
Unsure if this will help, but you should be able to run the emulator on a ARM64 based ( I tested on a M2 mac ) by passing in the platform flag to the docker run command. docker run --platform linux/x86_64 -it ghcr.io/goccy/bigquery-emulator:latest --project=test-project
I would like to propose adding support for the ARM64 architecture to the Docker image of the BigQuery emulator. With the increasing popularity and usage of ARM64-based systems, especially with the advent of ARM-based processors in both servers and personal computing devices, it is crucial for the Docker image to be compatible with these architectures.
Adding ARM64 support to the Docker image will:
I believe this enhancement will greatly benefit the community and align with the ongoing industry trend towards ARM64 adoption. Thank you for considering this request.
The text was updated successfully, but these errors were encountered: