liveBook · Manning

Entrypoint

As explained in Learn Docker in a Month of Lunches, Second Edition

A Traefik entrypoint is a named network entry point on which Traefik listens for external traffic.

When external traffic needs to reach containerized applications, an entrypoint gives Traefik a named listening port. Published container ports commonly map HTTP to 80, HTTPS to 443, and the dashboard to 8080. section 20.4

An entrypoint works as the front door for Traefik’s routing pipeline:

  • Receives traffic on a published port. section 20.4
  • Passes requests to routers, which match hostnames and paths before forwarding them to services. section 20.4
# remove nginx and the app containers:
docker container rm -f $(docker container ls -aq)
# start Traefik - connecting to a Linux Docker Engine:
docker compose -f traefik/docker-compose.yml `
 -f traefik/override-linux.yml up -d
# OR using Windows containers:
docker-compose -f traefik/docker-compose.yml `
 -f traefik/override-windows.yml up -d
# browse to http:/./localhost:8080

Start Traefik with Docker Compose, open its dashboard on port 8080, and inspect the configuration used for proxied applications. section 20.4

How Learn Docker in a Month of Lunches, Second Edition covers it

How deep it goes
Defines entrypoints as published container ports, but stops short of explaining socket-level implementation.
Examples
Uses ports 80 for HTTP, 443 for HTTPS, and 8080 for the Traefik dashboard.
What it assumes
Assumes basic Docker port publishing and reverse-proxy terminology.
What you can do after
Operate/configure Traefik by assigning published ports and verifying proxied requests through its dashboard.
How it connects
Connects entrypoints to routers, services, and middleware in Traefik’s request-processing path.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Learn Docker in a Month of Lunches, Second Edition. The section links point to the parts of the book it draws on.