`venice connectors` is hardcoded for port 8083

[nantrinh]

What if the user already has something running on 8083?

FIX:
kafka-connect in the docker-compose file should have

ports:
 - 8083

so the user's machine would map 8083 inside the container to an available port.

How to get this available port dynamically?

docker inspect kafka-connect prints out the port mappings of the container under NetworkSettings.
Here, my machine has mapped 8083 inside the container to 32791.
I would use localhost:32791 to connect to the container.

 "NetworkSettings": {
            "Bridge": "",
            "SandboxID": "01780fb640723155ae6c80589d773086cc5030f183993e2750d49df93a371d8e",
            "HairpinMode": false,
            "LinkLocalIPv6Address": "",
            "LinkLocalIPv6PrefixLen": 0,
            "Ports": {
                "8083/tcp": [
                    {
                        "HostIp": "0.0.0.0",
                        "HostPort": "32791"
                    }
                ],
                "9092/tcp": null
            },

You can get this port by running the following command

docker inspect --format='{{(index (index .NetworkSettings.Ports "8083/tcp") 0).HostPort}}' kafka-connect

https://docs.docker.com/engine/reference/commandline/inspect/#find-a-specific-port-mapping

This issue applies for the other hard-coded ports as well.

[DavidPerich]

I think rather then trying to grep the port the easiest solution is to justchange the external ports to on the docker-compose to something that is less likely to clash e.g 28083 instead of 8083.

I think there is a related problem of hardcoded localhost everywhere. I think the solution might be to prompt the user when the do venice up to set an network environment variable.

This would be good because it could allow us to then talk about how this still works with something like AWS or DO.