-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[WIP] CHE-120 Workspace creation as non-privileged container #4349
Conversation
Can one of the admins verify this patch? |
@l0rd am I correct that the plan is renaming |
FYI, I have also created an issue for publishing images to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @ibuziuk ! Some comments:
stacks.json
should not be modified, we are adding "modified" images just instacks.json.centos
- When modifying file
org.eclipse.che.ws-agent.script.sh
you should modifyorg.eclipse.che.ws-agent.json
- Instead of removing the sudo commands you could add and if condition that checks if the folder already exists (if the folder already exists the sudo command is not executed). With this approach other stacks will continue working.
…ctions for '/project' dir creation and package installation from ws-agent script to Dockerfile. Signed-off-by: Ilya Buziuk <ibuziuk@redhat.com>
@l0rd Thanks for review. PR has been updated
So, we are going to have smth. like that in build instructions :
?
Hmmm.. do not really understand why this should be done.
Good point - fixed |
You are right. A few months ago the shell script was duplicated in a json file but that should have been fixed now. |
What issues does this PR fix or reference?
https://issues.jboss.org/browse/CHE-120
Changelog
CHE-120 Workspace creation as non-privileged container