-
Notifications
You must be signed in to change notification settings - Fork 293
Open
Labels
Dockerwaiting-on-responseIf an issue goes without response for a while, close it.If an issue goes without response for a while, close it.
Description
Hello,
When I try to "sls deploy" using "dockerizePip: true" option, i get the following error:
Serverless: Invoke deploy
Serverless: Invoke package
Serverless: Invoke aws:common:validate
Serverless: Invoke aws:common:cleanupTempDir
Serverless: Installing required Python packages with python3.6...
Serverless: Docker Image: lambci/lambda:build-python3.6
Serverless: Linking required Python packages...
Error --------------------------------------------------
EEXIST: file already exists, symlink '/Users/me/project/test/lambda/.serverless/requirements/requirements.txt' -> './requirements.txt'
For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.
Stack Trace --------------------------------------------
Error: EEXIST: file already exists, symlink '/Users/me/project/test/lambda/.serverless/requirements/requirements.txt' -> './requirements.txt'
at Object.fs.symlinkSync (fs.js:1014:18)
I'm running on macOS, with latest sls version, and latest serverless-python-requirements version.
Thanks for your support.
Metadata
Metadata
Assignees
Labels
Dockerwaiting-on-responseIf an issue goes without response for a while, close it.If an issue goes without response for a while, close it.
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
AndrewFarley commentedon Nov 9, 2018
Can you post your serverless config file please?
kalote commentedon Nov 9, 2018
My requirements.txt:
kalote commentedon Nov 9, 2018
FYI, here is what i did from start:
Hope that helps :)
NOTE: After renaming requirements.txt into requirements, i don't have the issue anymore, BUT, the requirements are not packaged in the resulting zip file...
dschep commentedon Nov 12, 2018
Could you try
rm -rf .serverless
and re running (i think the pythonBin route is preferable in your casekalote commentedon Nov 12, 2018
dschep commentedon Nov 12, 2018
This is very odd. I tested this on macOS 10.13.4 and wasn't able to recreate the issue.
My test repo is https://github.com/dschep-bug-repos/sls-py-req-278
Could you follow the readme and confirm it causes this
EEXIST
issue for you too?kalote commentedon Nov 13, 2018
raethlo commentedon Mar 20, 2019
Hey all. I have had the same issue and after some trial&error I found out that the issue was fixed by upgrading the plugin (in my case it was a
3.x.x
->4.x.x
switch, so I suppose sth changed there). @kalote not sure if it's still an issue for you but anyways, for anybody that finds this thread, try runningsls plugin install -n serverless-python-requirements
.AndrewFarley commentedon Feb 28, 2020
Added a label for visibility, please comment if you or anyone can replicate this with the latest release of the serverless framework and this plugin, otherwise will close.
petergaultney commentedon May 30, 2020
I'm having a similar issue on 5.1.0.
I'm using poetry and Python 3.7.
i have very little relevant in my serverless file:
sls deploy
works just fine, butsirfuzzalot commentedon Oct 24, 2020
Having the same issue.
serverless deploy
works fine, butserverless deploy function
fails. Also on5.1.0
. Python3.8
. Serverless2.8.0
amediantsev commentedon Dec 2, 2021
@sirfuzzalot Have you resolved this issue?
brettdh commentedon May 24, 2022
Having the same issue since upgrading to serverless v3 and serverless-python-requirements 5.4.0. (I may have been seeing the same issue earlier, but it didn't seem as fatal, somehow.)
8 remaining items