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
docs: Add deployment documentation for chroot based minio deployments. #4659
Labels
Comments
@harshavardhana will take a look. |
harshavardhana
added a commit
to harshavardhana/minio
that referenced
this issue
Jan 6, 2018
9 tasks
harshavardhana
added a commit
to harshavardhana/minio
that referenced
this issue
Jan 7, 2018
harshavardhana
added a commit
to harshavardhana/minio
that referenced
this issue
Jan 9, 2018
harshavardhana
added a commit
to harshavardhana/minio
that referenced
this issue
Jan 11, 2018
nitisht
pushed a commit
that referenced
this issue
Jan 12, 2018
kaankabalak
pushed a commit
to kaankabalak/minio
that referenced
this issue
Jan 12, 2018
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It is quite easy to run
minio
being a static binary to run in a minimally ch-rooted environment - it makes it easy for user based namespace isolation on many standard Linux deployments.Expected Behavior
We need to document how to run minio in a chrooted environment.
Current Behavior
Currently there is no documentation regarding chroot based infrastructure for namespace isolation.
Possible Solution
Steps to Reproduce (for bugs)
Visit in docs.minio.io
Context
Deployment scenarios.
Your Environment
Current master branch.
The text was updated successfully, but these errors were encountered: