-
Notifications
You must be signed in to change notification settings - Fork 7
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
runs as root #8
Comments
The underlying container uses s6-overlay as init system. Since s6-overlay required read/write to rootfs, we only able to drop priv on the subprocess only. Is that what you looking for? |
I think so. Im automating doc processes and want to su other users and it
seems to fail if its not root which isvstrange.
…On Wed, Apr 17, 2024, 21:54 Socheat Sok ***@***.***> wrote:
The underlying container uses s6-overlay as init system. Since s6-overlay
required read/write to rootfs, we only able to drop priv on the subprocess
only. Is that what you looking for?
—
Reply to this email directly, view it on GitHub
<#8 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEFHWPNTAH5ZCJ6C7VAB46TY54YVPAVCNFSM6AAAAABFHRYPBCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRSHEYDCMBWHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I'm not sure if I understand correct but could you give some example? Are you process these docs through the REST API or via |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How do we set this image up to run as a user (uid/gid)?
The text was updated successfully, but these errors were encountered: