Back to browse
GitHub Repository

Automatic Port Forwarding for Docker Containers

2 starsGo

Conduit – Automatic Port Forwarding for Docker Containers

by orandaio·Feb 27, 2026·1 point·0 comments

AI Analysis

●●SolidSolve My ProblemShip It

Single-port multiplexing for Docker services, but Caddy and ngrok already handle this better.

Strengths
  • Abstraction over Codespaces/Dev Containers' inconsistent port exposure APIs
  • Zero configuration in container—runs directly inside without external setup
  • Linux-native implementation using /proc/net/tcp avoids dependencies
Weaknesses
  • HTTP-only routing—no WebSocket, gRPC, or TCP passthrough support
  • Linux-specific—/proc/net/tcp limits portability to Windows and macOS
Target Audience

Backend developers, DevOps engineers using Docker containers or dev environments

Similar To

Caddy · ngrok · socat

Post Description

A small Go library built to make it dead simple to expose internal ports from a Docker container (can be used anywhere, but this was my use-case).

I had trouble finding a simple tool to expose internal ports consistently. E.g. Codespaces, Dev Containers, etc have different mechanisms to expose ports.

To keep exposure agnostic, this tool can be run directly in the container.

Similar Projects

Open a Linux Container (for Mac)

Browser-accessible Linux shell in a container, but unclear what problem it solves.

Ship It
dpweb
203mo ago