-
-
Notifications
You must be signed in to change notification settings - Fork 431
Image provides tmpfs on /dev/shm #26
Comments
Are you sure this is something that's provided by this image? I haven't checked but I highly doubt it. If anything it's probably something that Docker itself adds |
Confirmed – there's no curl -s https://lambci.s3.amazonaws.com/fs/nodejs4.3.tgz | tar -t | grep '^dev/'
dev/
dev/stdout
dev/null
dev/random
dev/full
dev/urandom
dev/zero
dev/stderr
dev/stdin It appears that Docker adds this when it creates a container (ie, when you https://docs.docker.com/engine/reference/run/#runtime-constraints-on-resources Specifically the
Given that it must be greater than zero there doesn't seem to be a way to run a container without Docker adding it. You could specify it as one byte – that might have a similar effect? Or you'll have to rely on the complicated unmounting procedure you outlined. In any case, I don't think there's anything that can be done about the image itself on this front |
I will give that a go, thanks for the quick follow up @mhart ! |
@kadrach any success on this front? |
I ran into an issue earlier tonight trying to run chrome headless on lambda. It worked perfectly on the docker container but chrome never launched on lambda until I tracked down that lambda doesn't have |
Here are some things I tried which do not work: rm -rf /dev/shm
Permission error because we're not root (but we are) Overwrite /dev/shm
Nope, once again docker build discards the changes to /dev/shm.
|
|
The Lambda environment unfortunately does not have a tempfs mounted on
/dev/shm
, but it is provided by this image.I can manually fix this by running the container with
--privileged
, reinstallingutil-linux
(because/bin/mount
is missing) and unmounting/dev/shm
.Python's
multiprocessing
module uses/dev/shm
extensively and does not work properly in AWS Lambda, this is not fully replicated in this docker image.See issue on AWS forums.
However, this still runs on docker-lambda, but not on AWS Lambda:
The text was updated successfully, but these errors were encountered: