search

cloudfoundry-attic / cephfs-bosh-release

Apache License 2.0
10 stars 7 forks source link

ceph service bind with specific path issue #4

Closed marcus-sds closed 6 years ago

marcus-sds commented 7 years ago

I tried with volume path like below and the result mount path at container side was same. Which source should I check?

cf bind-service -c {"path": "/data"}

cf-gitbot commented 7 years ago

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/152569218

The labels on this github issue will be updated when the story is started.

marcus-sds commented 7 years ago

When I try with this '{"mount": "/var/vcap/data"}' option , it's working.

julian-hj commented 7 years ago

Yes, this is a known issue with AUFS. It will go away when Diego/Garden switches to GrootFS as the standard container file system, but for now, you have to specify a path with a top level folder that already exists. AUFS is not capable of creating new top level folders.

Having said that, I see that we do not have links to the troubleshooting guide in cephfs-bosh-release, so I will hold off closing this issue until we have fixed the cephfs README

julian-hj commented 6 years ago

This should no longer be an issue if you are using the latest version of cloud foundry--cf-deployment now uses GrootFS as the standard.

Also, we have linked troubleshooting instructions into CephFS. So I am going to go ahead and close this issue. Please feel free to reopen it or raise new issues if you still have problems.