You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I run a docker compose project where one service forwards the ssh agent into the container using /run/host-services/ssh-auth.sock, and before doing a colima stop, the project / service is not stopped, after a colima start the agent is not forwarded to the container correctly and it will fail with a connection refused.
This can be fixed by stopping all containers that use a SSH agent, stopping colima and restarting it.
Using colima ssh I did some checks and it seems that in the case where the issue occurs, /run/host-services/ssh-auth.sock is not a symlink to the agent file but a folder that contains a symlink to the agent.
manually removing that folder and creating a symlinks to the real agent file also fixes the issue.
Description
If I run a docker compose project where one service forwards the ssh agent into the container using
/run/host-services/ssh-auth.sock
, and before doing a colima stop, the project / service is not stopped, after a colima start the agent is not forwarded to the container correctly and it will fail with a connection refused.This can be fixed by stopping all containers that use a SSH agent, stopping colima and restarting it.
Using
colima ssh
I did some checks and it seems that in the case where the issue occurs,/run/host-services/ssh-auth.sock
is not a symlink to the agent file but a folder that contains a symlink to the agent.manually removing that folder and creating a symlinks to the real agent file also fixes the issue.
Version
colima version 0.6.7
git commit: ba1be00
runtime: docker
arch: x86_64
client: v24.0.7
server: v24.0.7
limactl version 0.19.1
qemu-img version 8.2.0
Copyright (c) 2003-2023 Fabrice Bellard and the QEMU Project developers
Operating System
Output of
colima status
INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: x86_64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
Reproduction Steps
see description
Expected behaviour
it should always correctly forward the agent.
Additional context
Created the base image using 0.6.6 as with 0.6.7 I have this issue: #930
The text was updated successfully, but these errors were encountered: