Re: shm

> So when I run out of shm in Kubernetes because of the 64MB limit, what is
actually causing it to run out?

on (postgres) docker it is a frequent problem and documented .. and the
result is a simple ERROR ... :(
and in: https://github.com/docker-library/docs/tree/master/postgres

*"Also note that the default /dev/shm size for containers is 64MB. If the
shared memory is exhausted you will encounter ERROR: could not resize
shared memory segment . . . : No space left on device. You will want to
pass --shm-size=256MB
<https://docs.docker.com/engine/reference/run/#runtime-constraints-on-resources>
for
example to docker run, or alternatively in docker-compose
<https://docs.docker.com/compose/compose-file/#domainname-hostname-ipc-mac_address-privileged-read_only-shm_size-stdin_open-tty-user-working_dir>"*
https://github.com/docker-library/postgres/issues/416
https://stackoverflow.com/questions/56839975/docker-shm-size-dev-shm-resizing-shared-memory

best,
Imre

Scott Ribe <scott_ribe(at)elevated-dev(dot)com> ezt írta (időpont: 2020. márc. 5.,
Cs, 15:43):

> What is POSIX shared memory used for anymore? Shared buffers now defaults
> to mmap, right? So when I run out of shm in Kubernetes because of the 64MB
> limit, what is actually causing it to run out?
>
> (I know about creating the memory-based volume and mounting it at
> /dev/shm, and have implemented that workaround. Still want to know what is
> causing this memory use.)
>
> --
> Scott Ribe
> scott_ribe(at)elevated-dev(dot)com
> https://www.linkedin.com/in/scottribe/
>
>
>
>
>
>