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

docker: works around zipkin-rabbitmq arm64 build fail in GHA deploy #3632

Merged
merged 1 commit into from
Dec 13, 2023

Conversation

codefromthecrypt
Copy link
Member

Currently, the docker deployment is failing on zipkin-rabbitmq on arm64. This isn't reproducable locally on either amd64 of arm64, but basically the rabbitmq-server crashes Dockerfile in an invalid way when building arm64:

BOOT FAILED
===========
Error during startup: {error,
                          {incompatible_feature_flags,
                              {disabled_required_feature_flag,
                                  classic_mirrored_queue_version}}}

What's invalid is that the same build which includes those features works outside the GHA runner. After spending a good bit of time on this, I gave up. Maybe a later version of qemu will sort it out.

Meanwhile, I switched the parent layer to the official docker image, and also switched to a configuration approach to define the default queue. I also noticed we have a bug in our collector logic where rabbit must be running prior to zipkin starting. This is a bug and I'll fix it later, but meanwhile it can be worked around with a dependency order in the example docker-compose file.

Currently, the docker deployment is failing on zipkin-rabbitmq on arm64.
This isn't reproducable locally on either amd64 of arm64, but basically
the rabbitmq-server crashes Dockerfile in an invalid way when building
arm64:

```
BOOT FAILED
===========
Error during startup: {error,
                          {incompatible_feature_flags,
                              {disabled_required_feature_flag,
                                  classic_mirrored_queue_version}}}
```

What's invalid is that the same build which includes those features
works outside the GHA runner. After spending a good bit of time on this,
I gave up. Maybe a later version of qemu will sort it out.

Meanwhile, I switched the parent layer to the official docker image, and
also switched to a configuration approach to define the default queue. I
also noticed we have a bug in our collector logic where rabbit must be
running prior to zipkin starting. This is a bug and I'll fix it later,
but meanwhile it can be worked around with a dependency order in the
example docker-compose file.

Signed-off-by: Adrian Cole <adrian@tetrate.io>
@codefromthecrypt codefromthecrypt changed the title docker: works around arm64 publish fail in GHA deploy docker: works around zipkin-rabbitmq arm64 publish fail in GHA deploy Dec 13, 2023
@codefromthecrypt codefromthecrypt changed the title docker: works around zipkin-rabbitmq arm64 publish fail in GHA deploy docker: works around zipkin-rabbitmq arm64 build fail in GHA deploy Dec 13, 2023
@codefromthecrypt
Copy link
Member Author

opened an issue on the unrelated ci flake #3633

@codefromthecrypt codefromthecrypt merged commit 02b8440 into master Dec 13, 2023
10 checks passed
@codefromthecrypt codefromthecrypt deleted the fix-rabbit branch December 13, 2023 05:31
@codefromthecrypt
Copy link
Member Author

Thanks for the offline advice @anuraaga!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants