-
Notifications
You must be signed in to change notification settings - Fork 293
Unable to add private repo to requirements.txt #560
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
Comments
Having the same issue, exact same error message. I am able to run the clone locally without issue. I am using RSA keys with a passcode. While the readme states that that should be ok, I'm going to try with new keys. |
Removing the password actually ended up removing the error, but this showed that this wouldn't be an ideal packaging so not looking at this further and will be using AWS Lambda layers. |
If you are using dockerized dependency installation, have a look at |
I think currently sls can not works with openssh key with passphrase Working with SSH key passphrases I failed also install packages in the docker from private repo. Only works when removing ssh key passphrase. Similar issue goes here #272 |
I have service that is dependent on a private github repo package. I added it to my requirements.txt but get the following error after sls deploy
Error: ERROR: Command errored out with exit status 128: git clone -q https://github.com/NielsHoogeveen1990/Test-predictor.git /tmp/pip-req-build-bqjgsle0 Check the logs for full command output.
How can I install a private repo?
The text was updated successfully, but these errors were encountered: