Upgrade from traefik:v2.0.0-alpha4 to traefik:v2.0.0-alpha6

Traefik Traefik v2 (latest)
1

I have working setup with traefik:v2.0.0-alpha4

  traefik:
    restart: unless-stopped
    image: traefik:v2.0.0-alpha4
    command:
     - --accesslog
     - --acme=true
     - --acme.acmeLogging=true
     - --acme.email=sergey@google.com
     - --acme.httpChallenge.entryPoint=http
     - --acme.onHostRule=true
     - --acme.storage=/acme/acme.json
     - --api
     - --entryPoints=Name:http Address::80
     - --entryPoints=Name:https Address::443 TLS
     - --log.level=debug
     - --providers
     - --providers.docker
     - --providers.docker.exposedByDefault=false
     - --providers.docker.watch
    labels:
      - traefik.enable=false
    ports:
      - 80
      - 443
      - 8080:8080
    volumes:
      - traefik:/acme
      - /var/run/docker.sock:/var/run/docker.sock
    networks:
      - public-web

so I want upgrade to traefik:v2.0.0-alpha6 (with the eventual goal of just pulling the latest traefik2 release, as they become available)

From hints I've seen in this forum, and from the slightly helpful debug messages, I know I have to change entryPoints to entrypoints.entryPoints when using slightly newer release of traefik 2.0

here is the config i use with traefik:v2.0.0-alpha6

  traefik:
    restart: unless-stopped
    image: traefik:v2.0.0-alpha6
    command:
     - --accesslog
     - --acme=true
     - --acme.acmeLogging=true
     - --acme.email=sergey@google.com
     - --acme.httpChallenge.entryPoint=http
     - --acme.onHostRule=true
     - --acme.storage=/acme/acme.json
     - --api
     - --entrypoints.entryPoints=Name:http Address::80
     - --entrypoints.entryPoints=Name:https Address::443 TLS
     - --log.level=debug
     - --providers
     - --providers.docker
     - --providers.docker.exposedByDefault=false
     - --providers.docker.watch
    labels:
      - traefik.enable=false
    ports:
      - 80
      - 443
      - 8080:8080
    volumes:
      - traefik:/acme
      - /var/run/docker.sock:/var/run/docker.sock
    networks:
      - public-web

I get the same messages at startup from traefik, between versions.

works fine with traefik:v2.0.0.-alpha4 .

I get no response in browser or with curl if I use traefik:v2.0.0-alpha6

traefik_1  | time="2019-07-04T03:48:52Z" level=debug msg="Creating middleware" entryPointName=https routerName=docker.nextcloud serviceName=nextcloud middlewareName=pipelining middlewareType=Pipeli
ning
traefik_1  | time="2019-07-04T03:48:52Z" level=debug msg="Creating wrr load-balancer" entryPointName=https routerName=docker.nextcloud serviceName=nextcloud
traefik_1  | time="2019-07-04T03:48:52Z" level=debug msg="Creating server 0 at http://172.24.0.5:80 with weight 1" routerName=docker.nextcloud serviceName=nextcloud entryPointName=https serverName=
0
traefik_1  | time="2019-07-04T03:48:52Z" level=debug msg="Added outgoing tracing middleware nextcloud" entryPointName=https routerName=docker.nextcloud middlewareType=TracingForwarder middlewareNam
e=tracing
traefik_1  | time="2019-07-04T03:48:52Z" level=debug msg="Creating middleware" middlewareName=traefik-internal-recovery middlewareType=Recovery entryPointName=https
traefik_1  | time="2019-07-04T03:48:52Z" level=debug msg="Creating middleware" entryPointName=traefik middlewareName=traefik-internal-recovery middlewareType=Recovery
traefik_1  | time="2019-07-04T03:48:52Z" level=debug msg="Creating middleware" entryPointName=http middlewareName=traefik-internal-recovery middlewareType=Recovery
traefik_1  | time="2019-07-04T03:48:52Z" level=debug msg="Try to challenge certificate for domain [nextcloud.google.com] founded in HostSNI rule" providerName=acme rule="Host(`nextcloud.google.com`)" routerName=next
cloud
traefik_1  | time="2019-07-04T03:48:52Z" level=debug msg="Looking for provided certificate(s) to validate [\"n.kvas.tech\"]..." routerName=nextcloud providerName=acme rule="Host(`nextcloud.google.com`)"
traefik_1  | time="2019-07-04T03:48:52Z" level=debug msg="Adding certificate for domain(s) nextcloud.google.com"
traefik_1  | time="2019-07-04T03:48:52Z" level=debug msg="No default certificate, generate one"
2

I fixed it by using following docker-compose.yml

  traefik:
    restart: unless-stopped
    image: traefik:v2.0.0-alpha8
    command:
     - --accesslog
     - --acme=true
     - --acme.acmeLogging=true
     - --acme.email=sergey@google.com
     - --acme.httpChallenge.entryPoint=http
     - --acme.onHostRule=true
     - --acme.storage=/acme/acme.json
     - --api
     - --entrypoints.http.address=:80
     - --entrypoints.https.address=:443
     - --log.level=debug
     - --providers
     - --providers.docker
     - --providers.docker.exposedByDefault=false
     - --providers.docker.watch
    labels:
      - traefik.enable=false
    ports:
      - 80
      - 443
      - 8080:8080
    volumes:
      - traefik:/acme
      - /var/run/docker.sock:/var/run/docker.sock
    networks:
      - public-web
3

Hi,

We recently redid the way Traefik handles configuration flags, which includes the way an entry point and its parameters are specified.

As reference for other uses with the same problem https://docs.traefik.io/v2.0/routing/entrypoints/#configuration

Duplicate of Traefik Docker provider error, entrypoints cannot be a standalone element