-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS Lambda Image Function: Error: ENOENT: no such file or directory, mkdir '/home/sbx_user1051/.serverless' #8983
Comments
Hello @ariel-frischer, thanks for reporting. In the case you're listing above it seems like there's a problem with using a read-only filesystem and |
Yes using docker my entrypoint |
@ariel-frischer What base image are you using when running |
|
If I could set the writable directory for serverless-offline to |
Are you setting the container to be nonwritable somehow locally? I'm afraid it's not a problem with the Framework itself but rather with your local setup or with |
Yes that is the base image where I run the command. What other files do you need me to provide? The dockerfile and handler? I can do that but I'm not sure if that will help. |
Thanks @ariel-frischer - I'm honestly a bit puzzled here because the error suggests that the command is running in one of |
Yea I've tried it coming across multiple different bugs when I try it that way as well. I've found a useful docker image to try to emulate here: adieuadieu/serverless-chrome#282 (comment) . I guess you can close the issue for now it seems to be more of an aws issue. |
What other bugs did you run into when running outside of docker container? As you suggested, I'm going to close this issue, but feel free to report back if you feel there's a bug that should be addressed on Framework side. |
I'm trying to deploy my full nodejs/express backend application using the serverless framework. Doing any normal
serverless deploy
does not work because it exceeds the 200Mb limit. So I've wrapped the application with a docker image and I've deployed a lambda function using this image. I've followed this article as a loose guide: https://espressocoder.com/2021/01/05/creating-a-serverless-docker-image/ with the goal of using theserverless offline
command to start this lambda function.This does not seem like a plugin issue, locally the plugins don't cause any errors so my
serverless.yml
is as follows.yarn serverless offline
outputInstalled version
The text was updated successfully, but these errors were encountered: