-
Notifications
You must be signed in to change notification settings - Fork 59
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
Make sudo work #46
Comments
I'm not familiar with Concourse CI so I would need to do some research. I don't understand why it would ignore the entrypoint.
The ability to run sudo seems like another odd assumption to make. What files?
I would much rather figure out another way around this problem. Even if I did do this I would make want to make it an argument to the entrypoint rather than be default, but if it is ignored that wouldn't be possible. If you need it NOW most immediate solution would be to build the image locally with /etc/sudoers set up as desired. |
Explicit design decision, I believe.
So the 'fetch sources' task runs as root, so if you're in the container as a non-root user you can't write to those files, or even the directory you're meant to write files to. Workaround is to
I suspected that would be the most effective way of progressing. |
I wanted to use Concourse CI with a crops/poky image. The first problem was that concourse ignores ENTRYPOINT and just drops into the image using the last user defined, which is
usersetup
. Annoying but worked around by using crops/yocto instead.Then I discover that basically to do a build with concourse I need to sudo as root to fix ownership of some files. Can you make password-less sudo work for the build user?
The text was updated successfully, but these errors were encountered: