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

Dockerfile.native - write access to /work directory #10395

Merged
merged 1 commit into from
Jul 1, 2020

Conversation

haraldatbmw
Copy link
Contributor

The Quarkus JTA implementation "JBoss Transactions" needs to write an object-store into the working directory and fails if the application has no write access.

Caused by: com.arjuna.ats.arjuna.exceptions.ObjectStoreException: ARJUNA012225: FileSystemStore::setupStore - cannot access root of object store: /work/ObjectStore/ShadowNoFileLockStore/defaultStore/

This pull-request changes the privileges and owner-ship of the /work directory without increasing the resulting docker-image size.

@boring-cyborg boring-cyborg bot added area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins area/platform Issues related to definition and interaction with Quarkus Platform labels Jul 1, 2020
@geoand
Copy link
Contributor

geoand commented Jul 1, 2020

Thanks for this.

Does a similar problem not occur in JVM mode?

@haraldatbmw
Copy link
Contributor Author

Thanks for this.

Does a similar problem not occur in JVM mode?

The Dockerimage for JVM has already these commands inside.

@haraldatbmw
Copy link
Contributor Author

I removed write access with my last pull-request #9091

@geoand
Copy link
Contributor

geoand commented Jul 1, 2020

Thanks for this.
Does a similar problem not occur in JVM mode?

The Dockerimage for JVM has already these commands inside.

Right, just saw it :)

Copy link
Contributor

@geoand geoand left a comment

Choose a reason for hiding this comment

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

Thanks!

@geoand geoand added triage/backport? triage/waiting-for-ci Ready to merge when CI successfully finishes labels Jul 1, 2020
@gsmet gsmet merged commit 26a37b7 into quarkusio:master Jul 1, 2020
@gsmet gsmet added this to the 1.6.0.Final milestone Jul 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins area/platform Issues related to definition and interaction with Quarkus Platform triage/waiting-for-ci Ready to merge when CI successfully finishes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants