Jx: JenkinsX install without full root access
Summary
I would like to be able to install jenkins-x without full root access. Obviously some things will require root access but I would like to be able to sudo only those options rather than the full install process
Steps to reproduce the behavior
- Be non-root
- Try to install jenkins-x
Expected behavior
I would expect it to install everything it can with my current permissions and then try to progress
Actual behavior
It fails almost instantly
Kubernetes cluster
local
alexanderrtaylor
All 6 comments
To clarify: 'jx install' doesn't require root access to run. But it is launching Docker containers that run processes as root and that is what I want to avoid. Specifically, my Kubernetes Volumes are on NAS servers that block root access. So any processes that write to Volumes (such as the JENKINS_HOME directory) need to run as a specific non-root user who has write access to the NAS file system. The same user ID can be used for all services (Jenkins, Nexus, MongoDB, ChartMuseum). That user may not be in the /etc/passwd file inside the various Docker containers, so the user must be specified by UID, not by name.
judahgreenblatt
on 25 Jun 2019
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale
jenkins-x-bot
on 12 Mar 2020
/remove-lifecycle stale
@abayer could I ask if I can help provide more evidence here or is it just pending investigation?
alexanderrtaylor
on 17 Mar 2020
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten
jenkins-x-bot
on 16 Apr 2020
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close
jenkins-x-bot
on 16 May 2020
@jenkins-x-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.
jenkins-x-bot
on 16 May 2020
Related issues
kevinsuperped
路
5Comments
empath
路
3Comments
tdcox
路
3Comments
vgallissot
路
5Comments
igdianov
路
3Comments
Most helpful comment
To clarify: 'jx install' doesn't require root access to run. But it is launching Docker containers that run processes as root and that is what I want to avoid. Specifically, my Kubernetes Volumes are on NAS servers that block root access. So any processes that write to Volumes (such as the JENKINS_HOME directory) need to run as a specific non-root user who has write access to the NAS file system. The same user ID can be used for all services (Jenkins, Nexus, MongoDB, ChartMuseum). That user may not be in the /etc/passwd file inside the various Docker containers, so the user must be specified by UID, not by name.