The goal is to run multiple Paladin Docker containers on the same node (using the localhost network). Each Paladin container should connect to a different Besu instance (node), and the Paladin containers should be able to communicate with each other.
It is assumed that the Paladin engine serves as the testbed, and the focus of this setup is to verify that the Paladin containers can communicate with each other and that they are receiving block events from the respective Besu nodes, as reflected in the logs.
This setup does not require a multi-cluster, multi-region, or multi-node deployment, but rather multiple containers running on a single local node.
Overview
The goal is to run multiple Paladin Docker containers on the same node (using the localhost network). Each Paladin container should connect to a different Besu instance (node), and the Paladin containers should be able to communicate with each other.
It is assumed that the Paladin engine serves as the testbed, and the focus of this setup is to verify that the Paladin containers can communicate with each other and that they are receiving block events from the respective Besu nodes, as reflected in the logs.
This setup does not require a multi-cluster, multi-region, or multi-node deployment, but rather multiple containers running on a single local node.
What needs to be done:
DoD