Skip to content
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

Cannot get ForwardAgent: true to work #66

Closed
neil-greenwood opened this issue Nov 23, 2021 · 2 comments · Fixed by #76
Closed

Cannot get ForwardAgent: true to work #66

neil-greenwood opened this issue Nov 23, 2021 · 2 comments · Fixed by #76
Labels
enhancement New feature or request
Milestone

Comments

@neil-greenwood
Copy link

I installed colima and docker through HomeBrew. I started colima, pulled an image and started a container. When I connect to that container, I see Could not open a connection to your authentication agent. when running ssh-add -L.
I then edited ~/.lima/colima/lima.yaml and added forwardAgent: true.

Even after killing the container and starting a new one, I still get no connection to the agent inside the container.

Am I doing something wrong?

@abiosoft
Copy link
Owner

@neil-greenwood it needs to be implemented directly in Lima.

Even though the visible config is at ~/.lima/colima/lima.yaml, it is being overwritten on every startup. Changing it manually will have no effect.

This will be fixed in the next version.

@neil-greenwood
Copy link
Author

Thanks. That's good to hear.
Is there any way to work around the issue in the meantime? I will try copying my public keys into the container, as a brute-force approach, if there's no other option.

@abiosoft abiosoft added this to the v0.3.0 milestone Nov 30, 2021
@abiosoft abiosoft added the enhancement New feature or request label Nov 30, 2021
@abiosoft abiosoft linked a pull request Dec 3, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants