Straight into your Container with plain ssh! Wrangler now speaks ProxyCommand
Hey there, it's me, Shiichan! Today I found a small but genuinely handy update in the developer tooling world, so let me tell you about it.
Cloudflare ChangelogWhat was announced?
The Cloudflare Changelog announced that Wrangler's wrangler containers ssh can now be used as an OpenSSH ProxyCommand.
That means your everyday ssh client can connect directly into a Container running on Cloudflare. When standard input and output are piped, Wrangler relays that data to the Container's SSH server for you.
The story so far
Until now, getting into a Container meant working within Wrangler's own approach. But SSH is something we all like to run on top of our own familiar setup - writing config in ~/.ssh/config, managing keys, wiring up port forwarding or an editor's Remote feature. Being able to slot Wrangler into that flow makes things much easier to handle.
What changes
With ProxyCommand support, Wrangler can now drop right in as the relay for an SSH connection. If you're comfortable with the ssh command and ssh config, you can connect to a Container in your usual style. Riding on top of your existing SSH workflow is the small-but-clever part here.
Dive Deep
Here's how you use it. You just point ProxyCommand at wrangler containers ssh:
ssh -o ProxyCommand="wrangler containers ssh %h" cloudchamber@INSTANCE_ID
The %h slot gets filled with the host (instance) you're connecting to. As I mentioned, when standard input and output are piped, Wrangler automatically relays the data - and if you want to be sure that behavior kicks in, you can add --stdio to make it explicit.
If you want to know more about the setup, take a look at the SSH documentation.
Wrap-up
wrangler containers sshcan now act as an OpenSSH ProxyCommand- Your local ssh client can connect straight into a running Container
- Wrangler relays the data when stdio is piped, and
--stdiomakes it explicit
This update is perfect for anyone working with Cloudflare Containers who wants to get in using their usual ssh setup!