-
Notifications
You must be signed in to change notification settings - Fork 19
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
Commands need root permission in Dockerfile-build of the project using MicroProfile framework #27
Comments
Hi @EunKyung-Kim, This is a known issue with the Liberty docker container, and we are actively pursuing a fix for this. In the meanwhile, your work around adding: |
@johnmcollier FYI. actually I had to add "USER root" to Dockerfile, not Dockerfile-build. The reason is that the command "RUN /opt/ibm/wlp/usr/extension/liberty_dc/bin/config_liberty_dc.sh" can be executed with root permission in Dockerfile generated by Microclimate. |
Hello Guys, I was having the same issue and the addition of the USER root now fixed the permission errors I was seeing but now the import stop in the following message, Any idea?[ERROR Thu Nov 1 02:28:03 UTC 2018 | Project: FileWatcher | File Name: /server/dist/controllers/projectsController.js | Function Name: getProjectInfoFromFile | Line Number: 631] Failed to find project information related to file /fwdata/projects/e73ae220-d7d2-11e8-99c8-eb2f635c11f0/e73ae220-d7d2-11e8-99c8-eb2f635c11f0.json |
Hello, |
Hi,
I remember this worked well at least 4 weeks ago. Since 2 weeks ago, webProfile7 docker image has been updated several times.
Anyway, I try to build the project of MicroProfile framework, but I meet the failure at the step for building the container image.
According to my log file, "mkdir -p /root/java" command failed with below error message. cannot create directory '/root': Permission denied
This command is one of Dockerfile-build.
Temporarily I added a command "USER root" to 2nd line in Dockerfile-build.
It looks like working well.
I think while originally generating Dockerfile-build this permission issue should be solved.
The text was updated successfully, but these errors were encountered: