Deployer started failing. sign_and_send_pubkey errors and others #3588
Replies: 2 comments 2 replies
-
Each run() call is in separate session. So no ssh agent keys persisted. Merge all three lines in single run() call. |
Beta Was this translation helpful? Give feedback.
2 replies
-
I think I'll overcome this issue by using access token for git. It doesn't really solve the pubkey error, but allows me to continue using Deployer. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I've been using Deployer quite successfully bout month and a half (migrated from a bit broken Envoy setup). But within the previous two weeks it started failing, and I don't know wether this is a Deployer issue or some other. I've been debugging this now quite some time and I've narrowed it down to some sort of ssh agent forwarding issue.
I have set up bot Deployer and Envoy to debug this issue. Deployer has following task:
and Envoy has similar setup with
Running Deployer gives following output:
Envoy task gives following (working) output:
These test were run on MacOS Ventura, M1 Apple against Ubuntu 20.04 server. Same behaviour can be seen with Intel Mac running Monterey.
To make things a bit weirder, when I run this through GitLab CI with Docker image built on php:8.2.5-cli, Deployer ssh portion works correctly. This would be a reasonable workaround but deploy fails elsewhere. It's probably something I should look more deeper into, but for some reason
release_or_current_path
gives alwayscurrent
and neverrelease
when deploying.release_or_current_path
works correctly when testing from local machine.I'd prefer to keep Deployer as my deployment solution as it gives a bit more pleasing DX than Envoy. Any ideas or suggestions where I should try next?
Beta Was this translation helpful? Give feedback.
All reactions