-
Notifications
You must be signed in to change notification settings - Fork 293
Private repos failing to install #272
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
Hmm that's odd. Could you provide some more environment details? IE OS, sls version, & plugin version. cc @cgrimal, Any idea why this might be failing? |
I'm on MacOS 10.13.6, serverless-python-requirements: 4.2.4, sls: 1.30.3 |
I get the same error if my ssh key is password protected, removing the password resolves the error. There is a mention of the ssh-agent in the
means in this context, if it only tells me to add the ssh-key prior to edit: MacOS 10.14.1 (18B75), serverless-python-requirements: 4.2.5, sls: 1.33.2 |
Try this:
The ssh-add command will ask for your password, and after that, the unencrypted ssh key is now living in that agent. You should be able to run the process normally after that point. Mac OS X manages ssh-agent for you, but on linux the |
This is what I did. It is not working. I get the same error as @woodpav but there is a longer stack trace I could post later. |
just to clarify, your private package is in your |
@dschep yes, exactly.
|
Issue confirmed. I think it's an issue with shell-quote turning |
Oh no 😞.
fixing |
commented on the wrong pr in the wrong repo |
See comment above, but i found:
so maybe we can't easily fix that issue? |
Hmm. you're right. I removed the |
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. |
good find ben! that is one hell of a hack tho 😂 |
Is there a way to specify which key gets used for said ssh access? For me personally it might be acceptable to create a separate deploy key (sans passphrase) to use for this. Alternately, is there a way to get access to the Docker host in a script? |
Any news on it? I did create a new key without password just for this, but I've notice that it just mount May we could at least add another custom parameter for using another key instead of id_rsa |
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 serverless#272 But it mey also be a interesting feature.
It worked for me as a workarround, but may be a feature. Here is it wviana#1 |
I am also unable to use docker with SSH_AGENT on macOS 10.14. I added keys and spawned the agent as normal but it isn't picking them up.
|
The solution I'm using is changing the code to copy my entire .ssh/ into contianer. |
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 |
i just made a different approach. it fixes the build-on-windows with private ssh keys problem. the drawback is ssh keys must be without passwords. pulls some based on https://nickjanetakis.com/blog/docker-tip-56-volume-mounting-ssh-keys-into-a-docker-container all files are in the same project root folder
and the
|
My
serverless.yml
is:I have my ssh key in
~/.ssh/id_rsa
(it's my only one). Installing the requirements works when I do not usesls deploy
.Changing to
dockerizePip: false
fixes the error. I'd like to usedockerizePip: true
.The text was updated successfully, but these errors were encountered: