-
I cannot run the Java agent with the self-hosting sidekick, but there is no problem if I connect this self-hosting with the NodeJS project.
|
Beta Was this translation helpful? Give feedback.
Answered by
boroskoyo
Dec 7, 2022
Replies: 1 comment 2 replies
-
Hi Minuth, the issue seems to be about your SIDEKICK_AGENT_BROKER_HOST setting the compose file. Since both broker and your app are expected to run in different containers, instead of 127.0.0.1, you should either give the container name (if they are defined in the same compose file) or the external IP of the host that runs the broker. You can also find extra information about docker networking on their docs: https://docs.docker.com/network/ |
Beta Was this translation helpful? Give feedback.
2 replies
Answer selected by
yasinkalafat
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Minuth, the issue seems to be about your SIDEKICK_AGENT_BROKER_HOST setting the compose file. Since both broker and your app are expected to run in different containers, instead of 127.0.0.1, you should either give the container name (if they are defined in the same compose file) or the external IP of the host that runs the broker. You can also find extra information about docker networking on their docs: https://docs.docker.com/network/