search

fullctl / ixctl

Apache License 2.0
2 stars 4 forks source link

Figure out ixctl -> aaactl comm issue when both containers are on the same box #34

Closed vegu closed 3 years ago

vegu commented 3 years ago

Problem

The ixctl container is unable to connect to the aaactl container for oauth purposes.

There are two versions of this issue

  1. aaactl has a public facing ip and a domain, but is running on a non-default port (e.g., not 80 and not 443), Opening a shell and trying to telnet to aaactl through the public facing ip will time out. This almost strikes me as a docker bug. Disabling the firewall on the host box was tried with no effect.

telnet test.vegu.net 8051 - timeout telnet test.vegu.net 80 - success

This issue goes away if ixctl is moved to a different host.

network_mode: "host" also fixes the issue, but introduces a bunch of other issues elsewhere.

  1. aaactl and ixctl are running non publicly (e.g., someone developing and running both in their os environment), aaactl does not have a publicly exposed website. I think this is more of a design / configuration issue where the networks for each need to be able to talk to each other.