Skip to content
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.

Sign up for GitHub

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

Jump to bottom

feature request: container filesystem perms #43

Closed
johnarnold opened this issue Jun 28, 2017 · 0 comments
Closed

feature request: container filesystem perms #43

johnarnold opened this issue Jun 28, 2017 · 0 comments

Comments

@johnarnold
Copy link

Reference: StackStorm/st2#3528

st2sensorcontainer runs as st2 user, not root. So, any files needed by sensor must have permissions for the st2 user inside the container. This requires doing things like chown -R st2 /etc/ssl/private or other files/directories required. It would be nice if there was a best practice / example for how to do this -- should you use a custom entrypoint.sh script to bin place stuff?
@johnarnold johnarnold changed the title feature/example request: feature request: container filesystem perms Jun 28, 2017
@LindsayHill LindsayHill mentioned this issue Jun 29, 2017
Closed
@arm4b arm4b closed this as completed in 6cc70fd Jul 17, 2020
transhapHigsn pushed a commit to DiligenceVault/st2-docker that referenced this issue Jun 8, 2021
Remove ALL-IN-ONE Docker deployment
ca5e3eb 
You can find the old deprecated version in `DEPRECATED/all-in-one` branch archive: https://github.com/StackStorm/st2-docker/tree/DEPRECATED/all-in-one

Closes StackStorm#22, closes StackStorm#23, closes StackStorm#26, closes StackStorm#29, closes StackStorm#34, closes StackStorm#41, closes StackStorm#43, closes StackStorm#92, closes StackStorm#112, closes StackStorm#117, closes StackStorm#125, closes StackStorm#133, closes StackStorm#141, closes StackStorm#145, closes StackStorm#151, closes StackStorm#163, closes StackStorm#187,
closes StackStorm#188, closes StackStorm#189, closes StackStorm#190
Closes StackStorm#162, closes StackStorm#138, closes StackStorm#108, closes StackStorm#102, closes StackStorm#65
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@johnarnold