ssh-agent changes the host socket name at each reboot in opensuse #8
Comments
StayPirate
added a commit
that referenced
this issue
Aug 12, 2021
Fix: #8 Before this commit, all the environment variables were initialized at container creation. Because of that, it was not possible to have different values in the subsequent execution, and this misbehaved in some circumstances, for instance in openSUSE Tumbleweed the $SSH_AUTH_SOCK value changes across each boot and the container is not able to start because it tries to bind mount a file that no longer exists. The design I implemented here is very similar to what secbox already does with resolv.conf [0]. Secbox now manages its own env-file which is updated and loaded every time an exec is called. [0] https://git.io/JR9fo
StayPirate
added a commit
that referenced
this issue
Aug 13, 2021
Fix: #8 Before this commit, all the environment variables were initialized at container creation. Because of that, it was not possible to have different values in the subsequent execution, and this misbehaved in some circumstances, for instance in openSUSE Tumbleweed the $SSH_AUTH_SOCK value changes across each boot and the container is not able to start because it tries to bind mount a file that no longer exists. The design I implemented here is very similar to what secbox already does with resolv.conf [0]. Secbox now manages its own env-file which is updated and loaded every time an exec is called. [0] https://git.io/JR9fo
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
the container won't be able to automatically start after a reboot in openSUSE TW (maybe leap too) because the
SSH_AUTH_SOCKenv variable and"${SSH_AUTH_SOCK}:/ssh-agent"bind mounted socket are defined at container creation time, and won't be the same after an host rebootThe text was updated successfully, but these errors were encountered: