Closed laserg closed 2 months ago
Hi @laserg, it looks like you are mixing up different methods assigning an IP. You can refer to the README file for the various methods used to bind an IP address to a service.
To clarify:
"BIND_IP=${GATEWAY_VM_IP}"
is the correct IP to use for services on the kop host, then that is the only config you needkop.bind.ip
from the portainer
serviceldap-user-manager
service looks correctYour logs, config and screenshot do not all agree with each other and so must not have been taken at the same time? For example, in the log output I see the correct IP you are looking for:
GATEWAY_VM_IP=192.168.0.86
time="2023-09-05T18:41:02Z" level=debug msg="writing traefik/http/services/ldap-user-manager/loadBalancer/servers/0/url = http://192.168.0.86:8081"
However this is different in the screenshot. Same with portainer, which is showing 192.168.16.2
in the screenshot but is configured to use 2.2.2.2
in the yaml config & the logs.
Hope this helps, let me know if you are still having trouble.
@chetan
Following your notes I made the minimal representative example Example, logs and screenshots attached.
Kop version: ghcr.io/jittering/traefik-kop:0.13.1
Steps to reproduce:
Expected result:
Obtained result:
P.S. All logs and screenshots taken at the same time. The only replacement made in logs and config is a domain.
@laserg the values written to redis by kop all look good to me. Have you checked the traefik logs to see what it's doing with those? Perhaps it's kicking it out for some reason or another. You may need to set traefik to debug to find out.
Under Weave Net should also local docker ip/port
https://github.com/weaveworks/weave
docker network ls
NETWORK ID NAME DRIVER SCOPE
3bc7409fa166 bridge bridge local
2bf42f32c591 docker_gwbridge bridge local
a6ac1aab6808 host host local
db87f193d2f1 none null local
cf7aaf23205a weave weavemesh local
VM IP: docker_gwbridge: ... inet 172.18.0.1
Container IP: ethwe0: ... inet addr:10.40.0.4
Traefik Server show URL http://172.18.0.3:80 It should find 10.40.0.4:80 instead of 172.18.0.3:80
@leotu I have not tried w/ weave, but the container networking support should cover that use case, I believe.
https://github.com/jittering/traefik-kop#container-networking
Do you have the traefik.docker.network
label set?
Hi. Thx for work and so... If I understand the idea correctly the BIND_IP is the ip used for publishing all the services in compose file. But on my config all services published by kop uses docker net ip insted of binded one.
I tried this two ways
The kop
docker-compose.yml
for same host case:The kop
.env
:The kop log is
The proof of ip binding is
![image](https://github.com/jittering/traefik-kop/assets/6731215/3b5256de-e487-4fe7-a439-6285067be5ad)
Expected IP is host 192.168.0.86