Fix SSH forwarding for exec process #506
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Reneechang17
force-pushed
the
renee/add-ssh-envvar
branch
from
8fa915a to
105ebd8
Compare
jglogan
approved these changes
Aug 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes SSH forwarding for exec processes.
Currently, only init processes received the
SSH_AUTH_SOCKenvironment variable when using--sshflag. Exec processes didn't have access to the SSH agent socket, even though the socket was mounted.Now we set environment variable for exec processes to match init process behavior, ensuring SSH forwarding works consistently across processes, and refactoring SSH forwarding condition into
hostSocketUrl()helper function.