Reverse Proxy

Reverse Proxy

Why? Port conflicts!

• Caused by multiple services on one host
• For example: Multiple stages of the same environment
• For example: Multiple web-based services using the same port

Reverse Proxy

• Routing of requests to correct container
• Based on Host header in HTTP
• Well-known: nginx, haproxy, traefik

Desired Features

• HTTP(S)
• Automatic wiring
• Automatic certificates

Reverse Proxy

HTTP: Routing based on Host header

HTTPS: Routing based on Server Name Indication (SNI)

–

Demo: Reverse Proxy

Automatic wiring using Traefik:

docker-compose up -d
IP=$(
  docker-compose ps -q proxy \
  | xargs docker inspect -f ''
)

Instead of publishing ports, you can also use network_mode: host.

Testing access to the registry frontend:

curl -s --resolve hub.me:80:$IP http://hub.me

Testing access to the registry API:

curl -s --resolve registry.me:$IP http://registry.me/v2/