uselagoon / uselagoon/lagoon-cli

Problem with ssh key with 1password ssh agent with WSL

Open
#446 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
28
Forks
14
Avg merge
1d 2h
Merged PRs (30d)
1

Description

Hi,

I have windows 11 with 1password ssh agent running. I have an ubuntu OS running on WSL and I have setup it to use the windows 1password agent in it (https://developer.1password.com/docs/ssh/integrations/wsl).

This is working. If I run ssh-add -L I see the ssh key I have on my windows 1password.
I can use git to get my code inside the Ubuntu without any problems. I even can ssh my lagoon project using the ssh command directly on the Ubuntu OS so the ssh agent is working correctly inside Ubuntu.

I then installed lagoon cli using brew and ran the lagoon config command.

The problem comes when I try to do lagoon login. It always gives me this error:

ssh: attempting connection using private key: /home/user/.ssh/id_rsa.

I then saved the public key in /home/user/.ssh/lagoon.pub file and changed the lagoon config to use it, following these instructions https://uselagoon.github.io/lagoon-cli/troubleshooting/#specific-key-in-agent.

Same result. Any idea on how to fix it?

Thank you

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Lagoon CLI troubleshooting guidance for a specific key in the agent, then reproduce the setup with ssh-add -L, lagoon config, and lagoon login under Ubuntu on WSL. Determine why login falls back to /home/user/.ssh/id_rsa; done means lagoon login uses the configured agent key successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, ubuntu
Domain
authentication, cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.