serverless-python-requirements: Private repos failing to install

My serverless.yml is:

plugins:
  - serverless-python-requirements
custom:
    pythonRequirements:
        dockerizePip: true
        dockerSsh: true

I have my ssh key in ~/.ssh/id_rsa (it’s my only one). Installing the requirements works when I do not use sls deploy.

Permission denied (publickey).
fatal: Could not read from remote repository.

Changing to dockerizePip: false fixes the error. I’d like to use dockerizePip: true.

About this issue

Original URL
State: open
Created 6 years ago
Comments: 21

Commits related to this issue

Update pip.js Add a `keyFile` option, so you could replace the default keyfile for one that is not `id_rds` This change was made to make possible a work arround for https://github.com/UnitedIncome... — committed to wviana/serverless-python-requirements by wviana 5 years ago

Most upvoted comments

good find ben! that is one hell of a hack tho 😂

dschep on Dec 10, 2018

I’m on MacOS 10.13.6, serverless-python-requirements: 4.2.4, sls: 1.30.3

woodpav on Oct 25, 2018

I can confirm the issue. I had to create a new set of key pairs without a passphrase, and following @wviana suggestion I had to manually amend pip.js to make it point to the new private key https://github.com/wviana/serverless-python-requirements/blob/be395cd2a7a36e50994949aaceed747f504efd7b/lib/pip.js#L197

AkA84 on Aug 3, 2020

I saw this referenced, it’s basically using a TTY channel to forward the socket into the container which is a total hack, but one of the less awful ways I can think of doing it.

bsamuel-ui on Dec 10, 2018

See comment above, but i found:

so maybe we can’t easily fix that issue?

smartinspereira on Dec 3, 2018