HUB
Sign inSign up

softfour/tcploadbalancer

By softfour

•Updated 13 days ago

Java TCP forwarding with configurable destination host, destination port and listening port.

Image
Networking
0

844

softfour/tcploadbalancer repository overview

⁠Softfour TCP Load Balancer

Java TCP forwarding container based on Eclipse Temurin JRE 21. The current Docker launcher passes one destination (TARGET_HOST:TARGET_PORT) to the bundled com.vrp.io.TcpLoadBalancer application.

The image exposes a single-target forwarding setup. Multiple-backend balancing, health-based failover and service discovery are not configured by the documented environment variables.

⁠Tags and platforms

TagRuntimePublished platform
latestEclipse Temurin JRE 21linux/amd64

Checked on 2026-11-08. The tag is updated in place; pin a digest for repeatable deployments. No native ARM64 variant is currently advertised.

⁠Quick start with Docker Compose

Replace backend.example.internal with a hostname reachable from the container, and set the destination port for your service:

services:
  tcp-proxy:
    image: softfour/tcploadbalancer:latest
    restart: unless-stopped
    environment:
      TARGET_HOST: "backend.example.internal"
      TARGET_PORT: "8080"
      BIND_PORT: "9090"
    ports:
      - "127.0.0.1:9090:9090"
docker compose config --quiet
docker compose up -d
docker compose logs --tail=100 tcp-proxy

The example makes the forwarded service available at 127.0.0.1:9090 on the Docker host. Use an appropriate host interface and firewall if remote clients need access. The destination is not created by this Compose file.

Equivalent docker run example:

docker run -d --name tcp-proxy   --restart unless-stopped   -e TARGET_HOST=backend.example.internal   -e TARGET_PORT=8080   -e BIND_PORT=9090   -p 127.0.0.1:9090:9090   softfour/tcploadbalancer:latest

⁠Runtime configuration

VariableDefaultPurpose
TARGET_HOSTlocalhostDestination hostname or IP, resolved/reached from inside the container
TARGET_PORT8080Destination TCP port
BIND_PORT9090Container listening port, bound on 0.0.0.0

localhost refers to this container, not the Docker host. Change TARGET_HOST for a destination outside the container. Changing BIND_PORT also requires updating the container side of the published-port mapping. The host port may differ, for example 127.0.0.1:19090:9090.

The launcher runs the JAR at /app/tcploadbalancer.jar and passes -l, -bindaddress and -port arguments from the values above. Configuration changes require recreating the container.

⁠Storage and security

No persistent application volume is required by this wrapper. Do not mount a directory over /app unless you intend to replace the bundled JAR.

This wrapper configures TCP forwarding, not TLS termination or client authentication. Any end-to-end encryption and authentication must be provided by the transported protocol and the destination service. Limit which clients can reach the listening port and which destination networks the container can access.

⁠Operations and troubleshooting

docker compose ps
docker compose logs --tail=100 tcp-proxy

Test the listener with a client for the forwarded protocol. For an HTTP backend, for example:

curl --fail-with-body http://127.0.0.1:9090/

For failed connections, check destination DNS, routing, port availability and firewalls. A running container alone does not prove the destination is reachable. The image does not declare a Docker health check.

⁠Upgrade and rollback

Record the image digest and retain the Compose configuration before upgrading:

docker compose pull tcp-proxy
docker compose up -d tcp-proxy

Confirm forwarding with the real application protocol. For rollback, use the previous softfour/tcploadbalancer@sha256:... digest and recreate the service.

⁠Maintenance and support

Maintained by Softfour⁠. For support, use your existing Softfour support channel and include the image tag, digest, platform and relevant logs with credentials removed.

The repository README is the source for this Docker Hub overview. Documentation updates do not change image contents. No versioned image changelog is currently published; record the digest before upgrading.

⁠License and upstream

The Java runtime is provided by Eclipse Temurin⁠. Contact Softfour for licensing information about the bundled TCP forwarding JAR. Third-party components retain their respective licenses. Contact Softfour for licensing information about image-specific files.

Tag summary

Content type

Image

Digest

sha256:581d747cb…

Size

110.1 MB

Last updated

13 days ago

docker pull softfour/tcploadbalancer