Traefik

How to use a private registry with docker swarm and traefik in docker

天大地大妈咪最大 提交于 2020-01-03 04:59:06
问题 I am running a single node swarm, I am using traefik to manage all my external connections, and I want to run a registry such that I can connect to it at registry.myhost.com Now all the examples I can see suggest creating a registry as a normal container rather than a service, however when I do this, I do not have the ability to add it to my traefik network and thus enable it to be found externally. Do I need to create another internal network and connect both traefik and it to it, and if so,

Docker container internal vs external dns resolution issue using Traefik

别来无恙 提交于 2020-01-03 03:51:08
问题 Docker 18.06.1-ce, traefik 1.7.3, dnsmasq, Mac 10.14 I have docker-compose setup with Traefik and need to access several services from inside the docker network/containers and externally. On a linux box (with Let'sEncrypt and http redirected to https), everything works using the same FQDN for both docker container internal and external access, and I don't have to use the service names. When I run curl http://belapi.dev.biodati.test from inside the pipeline container using docker-compose exec

HTTPS-Redirect with Traefik behind Aws Loadbalancer

谁说我不能喝 提交于 2019-12-31 03:48:08
问题 I'm trying to redirect all incoming Traefik from http to https, for a web application which gets served out of a docker container with a custom port. If I build this docker compose file, and scale the application everything works as expected. I'm able to request http and https of the application, but I try to accomplish that only https get served and http gets redirected to https. Since I use a Docker-Compose file, I don't have a Traefik.toml, and try to accomplish this without one. Docker

HTTPS request redirected to HTTP

孤街醉人 提交于 2019-12-25 01:27:33
问题 I am running Gunicorn behind a traefik ingress. HTTP is redirected to HTTPS by traefik, but for some reason gunicorn replies with a 301 pointing to HTTP. I have tried pretty much all the options I know off and didn't find any solution. I thought it might be related to something like https://stackoverflow.com/a/41488430/3719845. Here are the annotations I use on my ingress: kubernetes.io/ingress.class: traefik traefik.ingress.kubernetes.io/frontend-entry-points: http,https traefik.ingress

traefik - simple modification of URL

邮差的信 提交于 2019-12-24 22:25:25
问题 I want to modify the endpoints of my URL, while it goes from traefik to one of my containers. What I want is this. My URL looks like this - http://backend/asd and it should point to one of my containers with different endpoint like this - http://asd/dfg What I tried - asd: image: asd container_name: "asd" labels: - "traefik.backend=asd" - "traefik.frontend.rule=Host:backend;PathPrefixStrip:/asd,PathPrefix:/dfg" - "traefik.frontend.entryPoints=http" - "traefik.enable=true" - "traefik.port=80"

Secure communication between Ingress Controller (Traefik) and backend service on Kubernetes

℡╲_俬逩灬. 提交于 2019-12-24 08:56:38
问题 I'm trying to secure Nifi in a Kubernetes cluster, behind a Traefik proxy. Both are running as services in K8S. Traefik is secured with a public certificate. I want it to redirect calls to nifi, while securing the communication between Traefik (as an Ingress Controller) and the backend pods : Nifi. Looks like the secure confiuration should lire in my Ingress YAML descriptor. Looks like I should issue a CA root to generate Nifi self signed certificate and load this CA Root in Traefik so it can

How to use STS headers with Traefik when using Docker

Deadly 提交于 2019-12-24 07:37:54
问题 This is an issue I have been fighting with for days, but I could not find any help on stackoverflow, not even close to it. I hope to help people with similar issues in the future. Any elaboration on this question/answer is very much welcome. I have been trying to set STS-headers to http-requests when using Traefik as a proxy in a Docker environment. Somehow, no matter how I try to set the headers, my browser (Google Chrome) ignores them. What am I doing wrong? 回答1: I have been fighting with

How to make traefik work with graylog2?

社会主义新天地 提交于 2019-12-24 01:24:13
问题 I'm getting this error when entering to web interface url: Server currently unavailable We are experiencing problems connecting to the Graylog server running on http://127.0.0.1:9000/api. Please verify that the server is healthy and working correctly. You will be automatically redirected to the previous page once we can connect to the server. Do you need a hand? We can help you. More details docker-compose.yml: graylog: image: graylog2/server:2.3.0-1 environment: GRAYLOG_PASSWORD_SECRET: xxx

Mounting volume in Azure-Container-Service not working for traefik.toml and /var/run/docker.sock

泪湿孤枕 提交于 2019-12-24 00:44:11
问题 Building an CI/CD pipeline from VSTS to Azure-container-service I've ran into an issue mounting the traefik.toml and the docker.sock file. The deployment uses an SSH tunnel to create a folder /Deploy/ and copy the docker-compose.yml and traefik.toml. The files are there, the containers are spun up. Yet not handled by traefik, because it does not 'see' the containers. The traefik tutorial shows we can mount the like so in a docker-compose.yml : version: '2' services: proxy: build: context: .

Issues getting new httpChallenge working in Traefik 1.5.0-rc5

↘锁芯ラ 提交于 2019-12-24 00:42:23
问题 In trying to upgrade to the latest traefik version to be able to generate TLS certs from LetsEncrypt, I've come across a problem when it comes to cert generation time. This worked previously on traefik:1.4 using the acme.ondemand flag and the other settings (minus the httpChallenge keys of course). Config: traefik: image: traefik:1.5.0-rc5-alpine ports: - 80:80/tcp - 443:443/tcp command: - --web - --rancher - --rancher.metadata - --acme - --acme.email=my@email.com - --acme.onhostrule - --acme