I originally bumped into this post coming from google and went through the whole kubernetes issue and openshift workaround. Only to find the much simpler solution listed on another stackoverflow answer later.

added below line in deployment.yaml and container came up for me which was failing-
basically Mounting an emptyDir to /dev/shm and setting the medium to Memory

   spec:
     containers:
       - name: solace-service
         image: solace-pubsub-standard:latest
         volumeMounts:
           - mountPath: /dev/shm
             name: dshm
         ports:
           - containerPort: 8080
     volumes:
       - name: dshm
         emptyDir:
            medium: Memory

It's not possible to do this in a kubernetes pod. See this issue

There is a workaround from openshift mentioned in the comments, but it may not be ideal

EDIT: at the time this question was asked, this was not possible. It now is, see https://stackoverflow.com/a/47921100/645002 for the correct answer