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.

Sign up for GitHub

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

Jump to bottom

3.3.9 Containers fail to run with non-root user #14

Closed
arthurvanduynhoven opened this issue Aug 24, 2016 · 3 comments
Closed

3.3.9 Containers fail to run with non-root user #14

arthurvanduynhoven opened this issue Aug 24, 2016 · 3 comments

Comments

@arthurvanduynhoven
Copy link

When specifying a non-root user you get an error:

$ docker run -u 1000 -ti index.docker.io/maven:3.3.9-jdk-8 bash touch: cannot touch ‘/root/.m2/copy_reference_file.log’: Permission denied Can not write to /root/.m2/copy_reference_file.log. Wrong volume permissions?

In the main README it gives example about running as a non-root user but now fails with the addition/fix of issue #11 [https:/carlossg/docker-maven/commit/363ef271b86142d151f742fefa46d9d13bb656e6].

In the meantime I went back to maven:3.3.3 containers as it doesn't have this fix yet.

Thanks,

Art
@carlossg
Copy link
Owner

Just add -e MAVEN_CONFIG=..., I have updated the docs

JensErat added a commit to JensErat/basex that referenced this issue Aug 28, 2016
@JensErat
[FIX] Dockerfile: set m2 config directory
590bcda 
The upstream maven Docker image copies some files into the Maven config
directory during container startup, to fix some issues for images using
Maven at container runtime (see carlossg/docker-maven#11).

This broke startup for child images that do not run as root user (we're
adding a basex user). The same issue was described in
carlossg/docker-maven#14.

Resolves BaseXdb#1345, replaces BaseXdb#1346.
@JensErat JensErat mentioned this issue Aug 28, 2016
Merged
@dweomer dweomer mentioned this issue Sep 8, 2016
Closed
@dweomer
Copy link
Contributor

dweomer commented Sep 8, 2016 •
edited
Loading

Just add -e MAVEN_CONFIG=..., I have updated the docs

Is not acceptable as you have broken the ability for me to use this image within the Cloudbees Docker Pipeline plugin. See #16. I am very disappointed that this image, which used to work, has ceased to be useable within Jenkins.

Yes I could go back and modify all of my Jenkinsfiles but that is an unacceptable level of breakage in my opinion.

@steinsag steinsag mentioned this issue Mar 15, 2018
Closed
@carlossg
Copy link
Owner

see #16 (comment)

jenkinsci/docker-workflow-plugin#63 should have solved this without an image change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@carlossg @dweomer @arthurvanduynhoven