How can I avoid shm assertion when running in Docker container?

[CB1]

I created a simple docker container to run LibreOffice using Docker Toolbox on Windows 7 Pro. Here’s the full dockerfile;

FROM debian:stable
MAINTAINER cnkcb

ENV DISPLAY=192.168.99.1:0
ENV DEV_UID="1000"
ENV DEV_GID="1000"
ENV DEV_NAME="dev"
ENV DEV_HOME="/home/${DEV_NAME}"

RUN apt-get update                                      && \
    DEBIAN_FRONTEND=noninteractive apt-get -y upgrade   && \
    DEBIAN_FRONTEND=noninteractive apt-get -y install   \
        libreoffice default-jre openclipart-libreoffice \
        ttf-liberation                                  && \
    apt-get -y autoremove                               && \
    apt-get -y clean                                    && \
    groupadd -g ${DEV_GID} ${DEV_NAME}                  &&  \
    useradd -u ${DEV_UID} -g ${DEV_GID} -d ${DEV_HOME}  \
                    -m -s /bin/bash ${DEV_NAME}

USER ${DEV_NAME}
WORKDIR ${DEV_HOME}
VOLUME ["${DEV_HOME}"]

ENTRYPOINT ["libreoffice"]

CMD []

The container works very well UNLESS I mount the Docker volume. As soon as I do that, starting LibreOffice shows the following error in the console and exits;

dconf:ERROR:dconf-shm.c:92:dconf_shm_open: assertion failed: (memory != MAP_FAILED) 

You’ll note from the Dockerfile, there is a user dev and the docker VOLUME exposes the user’s home directory, which is \home\dev. This is a common pattern for me across several dockerfile, and I’ve never had a problem with it. I mount it to my C:\Users\CB and away I go.

I could change the dockerfile to mount say /home/dev/MyDocuments with C:\Users\CB\MyDocuments, but doing so (if it worked) would eventually cause the loss of the ~/.cache directory where a dconf and fontconfig live. I would very much prefer to avoid that.

Is this something that should be a bug, or am I missing some installation/configuration? Ideas?