Sign inSign up

sbx/github-ssh-kit

Verified Publisher

By Docker, Inc

Updated 9 days ago

Pre-populates GitHub host keys so SSH operations work without interactive host verification prompts.

Sandbox Kit
0

6.2K

sbx/github-ssh-kit repository overview

Digest

sha256:30453625adc3…

Size

2 Bytes

Schema

v2

Pushed

9 days ago

Specificationspec.yaml

MIXIN

Pre-populates GitHub host keys so SSH operations work without interactive host verification prompts.


Network Egress

github.com

api.github.com

Apply this mixin to a sandbox

sbx run <agent> --kit docker.io/sbx/github-ssh-kit:latest

Make sure you have docker sbx installed

Run the following command to install sbx on your machine.

macOS
brew install docker/tap/sbx
Windows
winget install Docker.sbx
Learn more about docker sbx

github-ssh

A mixin that pre-populates ~/.ssh/known_hosts with GitHub's host keys so SSH operations to GitHub work without interactive host verification prompts.

Without this kit, SSH connections from a sandbox to GitHub fail because there is no TTY available to interactively accept a new host key.

Prerequisites

Your SSH key must be loaded in the agent on the host and registered with your GitHub account. Start the sandbox with this kit attached, from its published OCI artifact on Docker Hub:

sbx run --kit "docker.io/sbx/github-ssh-kit:latest" claude

Or from a git URL targeting this repo:

sbx run --kit "git+https://github.com/docker/sbx-kits-contrib.git#dir=github-ssh" claude

Usage

Once the kit is installed, SSH operations to GitHub work without any additional configuration:

git clone [email protected]:org/repo.git
git push origin my-branch

Composing with git-ssh-sign

If you also want SSH commit signing, combine this kit with git-ssh-sign:

sbx run \
  --kit "git+https://github.com/docker/sbx-kits-contrib.git#dir=github-ssh" \
  --kit "git+https://github.com/docker/sbx-kits-contrib.git#dir=git-ssh-sign" \
  claude

How it works

At install time, the kit fetches GitHub's current SSH host keys from https://api.github.com/meta (the canonical source GitHub publishes) and appends them to /home/agent/.ssh/known_hosts. Using the HTTPS metadata endpoint works through HTTPS-only proxies where ssh-keyscan cannot reach port 22, and avoids hardcoding keys that GitHub may rotate.