Users on Diva Discord have been trying - with varied success - to connect the Diva stack with RocketPool and Eth Docker, with the CL and EL running there, instead of Diva.
The obvious answer is something like the ext-network.yml included here into COMPOSE_FILE. At that point however, Docker DNS creates issues for the reloader: Both RocketPool and Eth Docker also have a service called validator. I work around this by creating an alias vc-rkm that the reloader can connect to.
Strictly speaking this alias will only ever be needed in docker-compose.yml, but I also added it to docker-compose-with-clients.yml for consistency's sake.
This PR should serve as a discussion point - unless you see the obvious value and merge it right away that is ;)
This bears some explanation
Users on Diva Discord have been trying - with varied success - to connect the Diva stack with RocketPool and Eth Docker, with the CL and EL running there, instead of Diva.
The obvious answer is something like the
ext-network.ymlincluded here intoCOMPOSE_FILE. At that point however, Docker DNS creates issues for the reloader: Both RocketPool and Eth Docker also have a service calledvalidator. I work around this by creating an aliasvc-rkmthat the reloader can connect to.Strictly speaking this alias will only ever be needed in
docker-compose.yml, but I also added it todocker-compose-with-clients.ymlfor consistency's sake.This PR should serve as a discussion point - unless you see the obvious value and merge it right away that is ;)