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

Use variable for volume modifier because :Z does not play nicely on M1 #26327

Merged

Conversation

holly-cummins
Copy link
Contributor

Partial resolution of #25428. See also discussion in #25648. It looks like sometime between me raising #25648, @yrodiere fixing the elastic search part with #25663 , and me trying again some time later, a volume mount got added to the elasticsearch docker config. As per #25805, volume mounts need a different access modifier on M1.

Symptom being fixed: Build fails with setxattr … operation not supported

To test:

TESTCONTAINERS_RYUK_DISABLED="true" ./mvnw -Dquickly -DskipTests=false -Dstart-containers -Dtest-containers -f integration-tests/logging-gelf

Copy link
Member

@yrodiere yrodiere left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's... interesting. Yes, the modifier was necessary for tests to pass locally (f0c38b9). No idea why it worked before; maybe it didn't, maybe it only worked on specific OS/distros.

Anyway, good to know I should use that volume.access.modifier property instead of adding :Z like there's no tomorrow :)

LGTM, thanks!

@yrodiere yrodiere merged commit f79e07e into quarkusio:main Jun 24, 2022
@quarkus-bot quarkus-bot bot added this to the 2.11 - main milestone Jun 24, 2022
@holly-cummins
Copy link
Contributor Author

The moral of the story is that no good comes of having more than one platform architecture. :)

@holly-cummins holly-cummins deleted the holly-elasticsearch-volume-modifier branch June 24, 2022 08:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants