socat
Recipe card from the charly-infrastructure plugin (Images — the deployable catalog).
socat – Socket relay tool
Section titled “socat – Socket relay tool”Candy Properties
Section titled “Candy Properties”| Property | Value |
|---|---|
| Install files | charly.yml, task: |
Packages
Section titled “Packages”RPM: socat, iproute
Cross-distro coverage
Section titled “Cross-distro coverage”rpm: (Fedora), pac: (Arch), deb: (Debian/Ubuntu — socat, iproute2). Full parity.
my-image: candy: - socatTypically not added directly. Auto-included when a candy uses port_relay: in its charly.yml.
Note: Chrome no longer uses socat for its DevTools port relay. Chrome now uses a cdp-proxy Python supervisord service (see /charly-selkies:chrome). Socat is still used by other port_relay consumers.
Used In Boxes
Section titled “Used In Boxes”- Part of the
charlycandy’s full toolchain (used ingithubrunner)
Related Candies
Section titled “Related Candies”/charly-infrastructure:virtualization– part of thecharlycandy alongside socat/charly-infrastructure:gocryptfs– part of thecharlycandy alongside socat
When to Use This Skill
Section titled “When to Use This Skill”Use when the user asks about:
- Port relay setup (eth0 to loopback)
- socat configuration
- Exposing loopback-only services
- The
socatcandy orport_relayfield
Author + Test References
Section titled “Author + Test References”/charly-image:layer— candy authoring reference (tasks, vars, env_provide, tests block syntax)/charly-check:check— declarative testing framework for thecheck:block