Fix SSH commit signing when host uses 1Password#25
Open
Conversation
When the host configures `gpg.ssh.program` to use 1Password's `op-ssh-sign` binary, commit signing fails inside the container because that macOS-specific binary doesn't exist. DevContainers automatically forward SSH_AUTH_SOCK from the host, so the SSH agent (including 1Password's) is already available. By overriding `gpg.ssh.program` to `/usr/bin/ssh-keygen` in the container's local gitconfig (which is included after the host config), signing uses the standard ssh-keygen against the forwarded agent instead of the missing 1Password binary. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
gpg.ssh.programin the container's.gitconfig.localto use/usr/bin/ssh-keygeninstead of whatever the host has configuredop-ssh-signbinary, which doesn't exist inside the containerSSH_AUTH_SOCK, so the host's SSH agent (including 1Password's) is already accessible — only the signing program path needs to differTest plan
.gitconfigthat setsgpg.ssh.program = /Applications/1Password.app/Contents/MacOS/op-ssh-signgit commit -Ssucceeds inside the container using the forwarded SSH agent[include]directive in~/.gitconfig.local🤖 Generated with Claude Code