Skip to content
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

FeatureFlagService fails to run on Mac M1 Pro #396

Closed
saurabhdes opened this issue Oct 2, 2022 · 5 comments
Closed

FeatureFlagService fails to run on Mac M1 Pro #396

saurabhdes opened this issue Oct 2, 2022 · 5 comments
Labels
bug Something isn't working

Comments

@saurabhdes
Copy link
Contributor

saurabhdes commented Oct 2, 2022

Bug Report

Which version of the demo you are using? (please provide either a specific
Latest main or
b6e75ee

Symptom

What is the expected behavior?

FeatureFlag UI loads on going to http://localhost:8081/ so we can turn on different feature flags

What is the actual behavior?

FeatureFlag UI http://localhost:8081/ doesn't load on Mac M1 Pro

Reproduce

  • On Mac M1 Pro , follow the getting started steps for Docker https://github.com/open-telemetry/opentelemetry-demo/blob/main/docs/docker_deployment.md , essentially, docker compose up --no-build
  • Wait about 5min for containers to start
  • Notice featureflag container shows it's running
  • Look at the logs of feature flag service, you will see
    qemu: uncaught target signal 11 (Segmentation fault) - core dumped Segmentation fault
    My understanding is qemu is the upstream component used for running Intel (amd64) containers on M1 (arm64)
  • Then go to http://localhost:8081/ and notice the page doesn't load as expected

Additional Context

My best guess is the image available for featureflag service ghcr.io/open-telemetry/demo:v0.4.0-alpha-featureflagservice does not support ARM architecture. The same issue exists for other services but somehow they do seem to run successfully on M1.
refer below screenshot which shows a warning message on M1 for amd64 images.
Screen Shot 2022-10-01 at 6 24 33 PM

I think we need to build multi-arch images for all services with buildx and then push them to ghcr.

@saurabhdes saurabhdes added the bug Something isn't working label Oct 2, 2022
@janssenlima
Copy link

If you run docker compose up --build the image will be generated on your architecture and it will work. I went through this too and it's working.

@saurabhdes
Copy link
Contributor Author

@janssenlima That's correct and I am aware of it as well. It's a good workaround until this issue is resolved by building multi arch images that get pushed to ghcr as part of build pipeline.

@joshleecreates
Copy link
Contributor

This is resolved with @austinlparker's PR #536

I built v1.0.0 on amd64 and this error occurs when running the image under emulation with Docker Desktop on apple silicon
I applied the single line change (OTP v25->v23) then rebuilt on amd64 and the error does not occur on apple silicon.

@cartersocha
Copy link
Contributor

thanks @joshleecreates

@saurabhdes
Copy link
Contributor Author

Yes, now on my Mac M1 Pro as well after running docker compose up --no-build i am able to see feature flag service running successfully.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants