Mortom123 opened a new issue, #21088: URL: https://github.com/apache/pulsar/issues/21088
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Version OS: Win10 (Dockerhost), RHEL 8.8 (Container) Pulsar Container Version: "Latest" (as of right now, this points to 3.1.0, running in the container) ### Minimal reproduce step https://github.com/Mortom123/kotlin-io-example/ (thanks to @shibd) Follow the README.md: ``` docker-compose -f broker-compose.yml up -d mvn clean package docker-compose -f sink-compose.yml build docker-compose -f sink-compose.yml up ``` ### What did you expect to see? I expect to see no error logs and to succesfully boot the sink instance in a remote localrun setup. (Separate containers for broker and function worker) ### What did you see instead? kotlin-io-example-sink-1 | 2023-08-29T13:15:20,180+0000 [pulsar-client-io-1-4] WARN org.apache.pulsar.client.impl.ConnectionPool - Failed to open connection to localhost/<unresolved>:6650 : io.netty.channel.AbstractChannel$AnnotatedConnectException: finishConnect(..) failed: Connection refused: localhost/ 127.0.0.1:6650 The client.conf sets: ``` webServiceUrl=http://broker:8080/ brokerServiceUrl=pulsar://broker:6650/ ``` which are set through the docker-compose network, however the localrun command still tries to setup a connection to localhost. ### Anything else? The whole pulsar setup is containerized and ran using docker. It is important to use `localrun` because the sink itself will run in container and requires some native C-Libraries to bind against (not shown here), and I don't want to clutter the pulsar broker container with that. ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
