Issue with connecting multiple provider container networks #264
Labels
needs-kind
Indicates an issue or PR lacks a `kind/foo` label and requires one.
needs-priority
Indicates an issue or PR lacks a `priority/foo` label and requires one.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
Milestone
Right now, to run multiple provider containers, we start the first provider container by network name, and then start the other providers by the name of the first provider container. This is probably unnecessary, and can be cleaned up in a way to start each provider with the network name.
However, after attempting this, only the first running provider container connected to the analyzer even though inspection of the network showed all provider containers connected.
The text was updated successfully, but these errors were encountered: