You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 11, 2023. It is now read-only.
Many users (myself included) hit the issue of trying to access localhost from TriggerMesh components when using tmctl. Because the components run in containers, localhost does not resolve to the machine's localhost.
One idea would be for tmctl to produce a warning (non-blocking) to let the users know. Heres an idea of the message:
Warning: component <Kafka source | HTTP Poller source | ...> will run in a container, and localhost will refer to the container's localhost, not that of the host computer.
Depending on your environment, you may need to use a special hostname like host.docker.internal (for Docker Desktop) to access the localhost.
Some additional details are covered by [this blog post](https://www.triggermesh.com/blog/access-local-event-sources-with-tmctl-and-docker-desktop).
The text was updated successfully, but these errors were encountered:
Many users (myself included) hit the issue of trying to access localhost from TriggerMesh components when using tmctl. Because the components run in containers, localhost does not resolve to the machine's localhost.
One idea would be for tmctl to produce a warning (non-blocking) to let the users know. Heres an idea of the message:
The text was updated successfully, but these errors were encountered: