Closed bgounon closed 2 years ago
Hello,
The problem is related to the fact the port
flag is filled by an address instead of a port.
# version v1.5.0
$ whoami -port tcp://10.100.7.29:80
Starting up on port tcp://10.100.7.29:80
2021/12/03 18:32:25 listen tcp: address :tcp://10.100.7.29:80: too many colons in address
exit status 1
# version v1.6.0
$ whoami -port tcp://10.100.7.29:80
Starting up on port tcp://10.100.7.29:80
2021/12/03 18:31:42 listen tcp: address :tcp://10.100.7.29:80: too many colons in address
exit status 1
# version v1.7.0
$ whoami -port tcp://10.100.7.29:80
Starting up on port tcp://10.100.7.29:80
2021/12/03 18:34:04 listen tcp: address :tcp://10.100.7.29:80: too many colons in address
exit status 1
Maybe you have an env var called WHOAMI_PORT
with the value tcp://10.100.7.29:80
It seems related to a k8s behavior.
fixed by a067f0ee4c524f380f65ff4b5cb04aff9298d6dd
I will created a bug-fix release.
Hello, We're running whoami for testing purposes on our K8S Cluster, using latest DockerHub image. We're seeing a new issue today that we didn't have before. Pods fail to start with the following logs:
I see there has been a new release today, is it related ? I can reproduce at will by simply pushing the following configuration to a K8S cluster:
Edit: using image traefik/whoami:v1.6.1 fixes the issue