During its initialisation both rbd-target-api and rbd-target-gw try to
open /dev/log for their syslog handler. If the device is not present the
service fails to start. Thus expose /dev/log from the host in the
container solves that problem.
Signed-off-by: Sébastien Han <seb@redhat.com>
--cap-add=ALL \
--net=host \
-v /dev:/dev \
+ -v /dev/log:/dev/log \
-v /lib/modules:/lib/modules \
-v /etc/ceph:/etc/ceph \
-e CLUSTER={{ cluster }} \
--cap-add=ALL \
--net=host \
-v /dev:/dev \
+ -v /dev/log:/dev/log \
-v /lib/modules:/lib/modules \
-v /etc/ceph:/etc/ceph \
-e CLUSTER={{ cluster }} \