Read-only log dir mounting for log-forwarding add-ons? about bpm-release

[cf-gitbot]

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

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

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

[voelzmo]

+1 It would be great if blackbox didn't need to run on the VM directly, but could also run in a container.

[xoebus]

This should now be possible by using the new unrestricted volumes feature. Could you give that a try and let us know if it works for you?

e.g. Mount /var/vcap/sys/log into the blackbox job.

[xoebus]

I'm going to close this based on my suspicion that the unrestricted volumes fixes it. If I'm wrong then please feel free to open a new issue referencing this one.

[anEXPer]

It probably solves not being able to run blackbox in BPM at all, don't know when I'll be able to try it (syslog is not currently allocated engineering team, so I'm working on it as a flex project).

I don't see any provision to have read-only access, did I just miss that, or is it not part of this yet?

[xoebus]

It's read-only by default and then you can opt a volume in to being writable.

[anEXPer]

Cool, that should work exactly the way we want it, thanks.