Menu
I'm running Chrome with xvfb on Debian 8. It works until I open a tab and try to load content. The process dies silently...
Fortunately, I have gotten it to run smoothly on my local docker using docker run --shm-size=1G.
There is a known bug in Chrome that causes it to crash when /dev/shm is too small.
I am deploying to Container engine, and inspecting the OS specs. The host OS has a solid 7G mounted to /dev/shm, but the actual container is only allocated 64M. Chrome crashes.
How can I set the size of /dev/shm when using kubectl to deploy to container engine?
365
Docker containers are allocated 64 MB of shared memory by default.
You can modify shm size by passing the optional parameter --shm-size to docker run command. The default is 64MB.
A container engine is a piece of software that accepts user requests, including command line options, pulls images, and from the end user's perspective runs the container. There are many container engines, including docker, RKT, CRI-O, and LXD.
Mounting an emptyDir to /dev/shm and setting the medium to Memory did the trick!
spec: volumes: - name: dshm emptyDir: medium: Memory containers: - image: gcr.io/project/image volumeMounts: - mountPath: /dev/shm name: dshm If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With