Problem with port number about caddy-docker-proxy HOT 3 CLOSED

This would be more a docker-compose issue.
There is a workaround on json (see https://stackoverflow.com/questions/24480835/decoding-json-int-into-string)
Maybe a pull to docker-compose...

from caddy-docker-proxy.

Since string is compatible with both docker-compose and docker swarm, I guess we can change our demo to use port as string.

But the demo is still made for docker swarm, you would still have to change version to 2 to be able to use it with docker-compose.

from caddy-docker-proxy.

This was fixed on c8f9152

That's a docker-compose issue, it doesn't handle labels as numbers, only strings.
I changed our demo to make it more compatible with docker-compose, in case someone tries to use docker-compose to run it in the future.

Thanks

from caddy-docker-proxy.