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

Jib jvm build permissions issues #23665

Closed
doczico opened this issue Feb 14, 2022 · 5 comments · Fixed by #23670
Closed

Jib jvm build permissions issues #23665

doczico opened this issue Feb 14, 2022 · 5 comments · Fixed by #23670
Labels
area/container-image kind/bug Something isn't working
Milestone

Comments

@doczico
Copy link

doczico commented Feb 14, 2022

Describe the bug

While creating a container image using jib (fast-jar) the whole /work folder (content included) is created with 755 and root as owner even when the username is specified or the image run as another user.
which in my case lead to this issue
Caused by: com.arjuna.ats.arjuna.exceptions.ObjectStoreException: ARJUNA012225: FileSystemStore::setupStore - cannot access root of object store: ObjectStore/ShadowNoFileLockStore/defaultStore/

Expected behavior

the /work folder and sub directories to be created with the specified (or image default) user as owner

Actual behavior

the /work folder is created with root as owner

How to Reproduce?

use jib to build the container image as fast-jar

Output of uname -a or ver

No response

Output of java -version

11

GraalVM version (if different from Java)

No response

Quarkus version or git rev

2.7.1

Build tool (ie. output of mvnw --version or gradlew --version)

3.8

Additional information

No response

@doczico doczico added the kind/bug Something isn't working label Feb 14, 2022
@quarkus-bot
Copy link

quarkus-bot bot commented Feb 14, 2022

/cc @geoand

@geoand
Copy link
Contributor

geoand commented Feb 14, 2022

Thanks for reporting!

How can reproduce this issue?

@doczico
Copy link
Author

doczico commented Feb 14, 2022

kind of similar to #2702 and #21573

with quarkus 2.7.1 and jib extension build a container image with
maven clean package -Dquarkus.container-image.push=true for example and check inside the container the /work folder permission

@geoand
Copy link
Contributor

geoand commented Feb 14, 2022

#23670 takes care of the issue

geoand added a commit that referenced this issue Feb 14, 2022
Update working directory for Jib created images
@quarkus-bot quarkus-bot bot added this to the 2.8 - main milestone Feb 14, 2022
@gsmet gsmet modified the milestones: 2.8 - main, 2.7.2.Final Feb 21, 2022
@doczico
Copy link
Author

doczico commented Feb 25, 2022

Thank you very much for the (ultra) quick fix

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

Successfully merging a pull request may close this issue.

3 participants