Skip to content

Commit badf32f

Browse files
author
Julian Hjortshoj
authored
Update README.md
remove out of date note about aufs mount path limitations
1 parent f0b2e53 commit badf32f

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

README.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -224,7 +224,6 @@ container, you can use the `mount` key from within your bind configuration:
224224
```bash
225225
cf bind-service myapp mybucket -c '{"mount":"/var/something"}'
226226
```
227-
> NOTE: As of this writing **aufs** used by Garden is not capable of creating new root level folders. As a result, you must choose a path with a root level folder that already exists in the container. (`/home`, `/usr` or `/var` are good choices.) If you require a path that does not already exist in the container it is currently only possible if you upgrade your Diego deployment to use [GrootFS](https://github.com/cloudfoundry/grootfs-release) with Garden. Soon, GrootFS will become the standard file system for CF containers, and this limitation will go away.
228227

229228
### Remote Connections to Service Instances
230229

0 commit comments

Comments
 (0)