microservices-demo: Unable to build / deploy on ARM

 - deployment/adservice: container server terminated with exit code 1
    - pod/adservice-5b65c5ff6-zzfkl: container server terminated with exit code 1
      > [adservice-5b65c5ff6-zzfkl server] Error occurred during initialization of VM
      > [adservice-5b65c5ff6-zzfkl server] Could not find agent library /opt/cprof/profiler_java_agent.so in absolute path, with error: /opt/cprof/profiler_java_agent.so: cannot open shared object file: No such file or directory (Possible cause: can't load AMD 64-bit .so on a AARCH64-bit platform)
 - deployment/adservice failed. Error: container server terminated with exit code 1.

About this issue

  • Original URL
  • State: open
  • Created 5 years ago
  • Comments: 25 (10 by maintainers)

Most upvoted comments

For anyone in this thread who would like to test again, this https://github.com/GoogleCloudPlatform/microservices-demo/pull/2589 has been merged into main. No new associated container image, but if you build them locally, this should now work.

Update (Jan 2023)

Supporting ARM is definitely a priority for 2023. […] We hope to achieve this by the end of this year (2023).

Hey, we bumped into this, wanting to use the demo as part of our testing pipeline that runs on arm64 cilium/tetragon#2345. Do you still want to publish arm64 images anytime soon? Thanks!

By the way, I hope it’s not inappropriate to write about “alternatives”, but for people looking for similar demos working both on amd64 and arm64, we ended up using https://github.com/open-telemetry/opentelemetry-demo.

Not fully supported yet, but note that you can alternatively use docker buildx from your ARM machine to build amd64 images: https://docs.docker.com/buildx/working-with-buildx/#build-multi-platform-images

We’re currently investigating the use of ARM chips by developers to build our sample applications.

tl;dr - We will not be (consciously) supporting the deployment of our microservice sample images on ARM anytime soon. I say “consciously” because you might still be able to build the Docker images locally (and target ARM) and get them to deploy on ARM machines.


Hi @zwan2 and @jxlwqq! Thank you for raising this issue! 😁

We’ve actually been talking about ARM support a lot recently. This issue is becoming a growing concern — especially given the popularity of the M1 chip.

Currently, the Docker images (for each microservice) that we host (e.g., gcr.io/google-samples/microservices-demo/checkoutservice:v0.3.1) use AMD64 architecture.

> docker image inspect gcr.io/google-samples/microservices-demo/checkoutservice:v0.3.1 | grep Arch
"Architecture": "amd64",

And, unfortunately, we do not intend to create sample images that use ARM architecture anytime soon — mainly because Google Kubernetes Engine does not currently support ARM-based image deployments.

@zwan2 In your Kubernetes deployments, are you using the images hosted at gcr.io/google-samples/microservices-demo/...? If so, have you tried building the images locally (and targeting ARM) and using those locally-built Docker images in minikube? I can’t guarantee that this works (because I am not sure if the base images used in each of microservices’ Dockerfiles support ARM). But it’s worth trying. 😃

Update (Jan 2023)

Supporting ARM is definitely a priority for 2023. […] We hope to achieve this by the end of this year (2023).

Hey, we bumped into this, wanting to use the demo as part of our testing pipeline that runs on arm64 https://github.com/cilium/tetragon/pull/2345. Do you still want to publish arm64 images anytime soon? Thanks!

Update (Jan 2023)

Supporting ARM is definitely a priority for 2023.

More specifically:

  • A user should be able to run Online Boutique in development mode (skaffold dev), on an ARM-based device.
  • A user should be able to deploy Online Boutique, as is, on an ARM-based Kubernetes cluster. In this sentence, “as is” means that the user does not have to build Online Boutique’s container images themselves. Official ARM-supporting container images should be published by Online Boutique.

We hope to achieve this by the end of this year (2023).

Thank you, @smazzone and @GregCKrause for the tips you’ve shared — those will be helpful.

@GregCKrause I have been running the demo on arm64 for a couple of weeks. I have also used buildx to build images on both architectures. But, changing skaffold.yaml was not enough. I had to slightly re-adapt Dockerfile as health probes are hardcoded for amd64 architecture see example here

RUN GRPC_HEALTH_PROBE_VERSION=v0.4.14 && \ wget -qO/bin/grpc_health_probe https://github.com/grpc-ecosystem/grpc-health-probe/releases/download/${GRPC_HEALTH_PROBE_VERSION}/grpc_health_probe-linux-amd64 && \ chmod +x /bin/grpc_health_probe

I hope this helps. Stefano

Does not support deployment it under arm64 architecture, such as Apple chip’s Mac, Raspberry Pi. @zwan2

Are there any plans to support arm64? @ckim328

  • m1 mac Big Sur 11.6x
  • minikube:latest using docker

It may be resolved when x86 condition