AWS Lambda runs out of space with repeated invokations with `zip=True`

[dschep]

module initialization error: [Errno 28] No space left on device

This seems to be because the zip option extracts to a random tempfile, and when the lambda is kept warm, that quickly eats through the 512MB of available tempspace. Need to extract to a fixed path instead.

[petergaultney]

Is it possible that this could still be happening under certain circumstances?

I've got scapy as a dependency, so I'm using the following serverless config:

  pythonRequirements:
    dockerizePip: 'non-linux'
    zip: true

and the corresponding

try:
    import unzip_requirements  # noqa
    print('succesfully imported unzip_requirements to prepare the zipped requirements')
except ImportError:
    print('failed to import unzip_requirements - if you are running locally this is not a problem')

And though my serverless function deploys successfully, it dies early during runtime, with the very undescriptive logs

START RequestId: 8c765d18-bc46-11e8-b10d-27090ffc586e Version: $LATEST
module initialization error: [Errno 28] No space left on device
END RequestId: 8c765d18-bc46-11e8-b10d-27090ffc586e
REPORT RequestId: 8c765d18-bc46-11e8-b10d-27090ffc586e	Duration: 11873.90 ms	Billed Duration: 11900 ms Memory Size: 2048 MB	Max Memory Used: 841 MB	
module initialization error
[Errno 28] No space left on device

Note that this is on the first invocation, so I suppose this is probably a new issue.

[dschep]

Yes, see #243.