Great, thanks for the clarification Amit !toggle quoted message Show quoted text
On Mon, Mar 21, 2016 at 5:08 PM, Amit Gupta <agupta(a)pivotal.io> wrote:
If you push a docker container via cf ((not directly to Diego API) it's
hard coded to run unprivileged.
Set this to true:
Set the "url" for the Diego release in your manifest to
"file:///PATH-TO-DIEGO-REPO" and the version to "create", this will create,
upload, and use your local release next time you bosh deploy.
On Monday, March 21, 2016, Guillaume Berche <bercheg(a)gmail.com> wrote:Hi Ted,
What's the procedure to enable privileged containers in a CF deployment ?
I could not yet find related properties in diego-release, or
Do I understand correctly from  that applications pushed through
buildpack run in privileged containers by default and hence can use FUSE
clients, whereas docker-based CF apps run in non-priviledged containers 
Thanks in advance,
On Tue, Mar 15, 2016 at 10:29 PM, Ted Young <tyoung(a)pivotal.io> wrote:Hi Raymond,
It is possible to use FUSE-based clients to connect to remote
filesystems, but only if your Cloud Foundry deployment has enabled
We are currently working on adding volume management to Cloud Foundry.
NFS and other distributed filesystems will be available as services,
allowing access without the need for privileged containers or FUSE.
On Tue, Mar 15, 2016 at 1:21 PM, Raymond J Steele <
raymondsteele(a)gmail.com> wrote:Can a cloud foundry application make us of Network Filesystem share? If
so, would this scale?