Can we have a simpler image structure, perhaps as an extra option. I've been running Traefik in my FreeBSD Kubernetes cluster, using upstream's helm charts. This did not work with the current s6-based image structure because the helm charts assume that Traefik is the image entrypoint and the generated deployment uses Traefik's command-line arguments to configure the proxy instead of a file. Some docker compose examples (e.g. https://doc.traefik.io/traefik/expose/docker/basic/) also assume this.
I'm using this Containerfile for my local experiments:
FROM ghcr.io/freebsd/freebsd-runtime:15.0
RUN pkg bootstrap -y -r FreeBSD && pkg -o IGNORE_OSVERSION=yes update -f
RUN pkg install -y traefik
RUN pkg clean -ay && pkg delete -fy pkg && rm -rf /var/db/pkg/repos
ENTRYPOINT [ "/usr/local/bin/traefik" ]
Note, this could (should?) use more restricted images such as freebsd-staticto reduce the attack surface for a publicly reachable proxy. On the other hand, upstream uses alpine as base (https://github.com/traefik/traefik/blob/master/Dockerfile) so perhaps that isn't necessary.
Can we have a simpler image structure, perhaps as an extra option. I've been running Traefik in my FreeBSD Kubernetes cluster, using upstream's helm charts. This did not work with the current s6-based image structure because the helm charts assume that Traefik is the image entrypoint and the generated deployment uses Traefik's command-line arguments to configure the proxy instead of a file. Some docker compose examples (e.g. https://doc.traefik.io/traefik/expose/docker/basic/) also assume this.
I'm using this Containerfile for my local experiments:
Note, this could (should?) use more restricted images such as freebsd-staticto reduce the attack surface for a publicly reachable proxy. On the other hand, upstream uses alpine as base (https://github.com/traefik/traefik/blob/master/Dockerfile) so perhaps that isn't necessary.