Reputation: 9431
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?
Upvotes: 59
Views: 46179
Reputation: 1
docker run --shm-size 2G ubuntu:latest
to run container locally where
--shm-size 2G
is used to tweak shm available size.
Upvotes: -12
Reputation: 669
In my case it was the resource limit which was causing the issue. It was set to 128 MB earlier then I changed it to 1 Gigs and it started working.
resources:
limits:
cpu: 300m
memory: 128Mi
Changed to:
resources:
limits:
cpu: 300m
memory: 1Gi
Upvotes: 0
Reputation: 9431
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
Upvotes: 184