Closed joaomcarlos closed 3 years ago
Hi @joaomcarlos, Thanks for reporting the issue!
Let me try recreating the error using your pipfile and get back to you.
Hi @joaomcarlos, appologies for the late reply. Just recently got some time to look into this issue. I tried retracting the error but was unsuccessful. The scripts to setup the test environment can be found in https://github.com/ketgo/nameko-kafka/tree/Issue-2/tests/test_container. Basically the setup involves starting a zookeeper , kafka and a sandbox container using docker-compose. Since the reported issue involves DNS lookup error, I used a virtual network for which docker creates an internal DNS. The sandbox container installs all the packages using your shared pipfile. Upon running the tests there were no issues reported. You can run this locally by:
$ git clone --single-branch --branch Issue-2 https://github.com/ketgo/nameko-kafka.git
tests/test_container
folder$ docker-compose up -d --build
This starts the zookeeper, kafka and sandbox containers. The sandbox image is first built using the Dockerfile present in the folder.
$ docker-compose logs sandbox
You would have to re-run the above command to check on the progress of the tests.
Please let me know if something is missing in the setup.
Note: I have commented out the package downloaded from private python pip repo in the pipefile.
Thanks, Ketan
Closing issue due to inactivity.
Hi,
I updated to version 0.2 and my microservice stopped working when its inside a container but I also later tested it when on my host machine.
This is the message I get:
I noticed the pipfile.lock has a few "sub-packages" that were updated, could the problem be in one of those?
This seems to happen on the "return trip" from the server, after processing the "advertised hosts". I can confirm that I can access the Kafka server just fine with version 0.1 by forcing the version on the pipfile.
Contents of my pipfile
Contents of my pip.lock file