feat(docker): custom network support #49
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
config
andinstall
wizard screens to allow config of custom docker network if runMethod == docker.docker.Start()
and subsequently tears it down onStop()
.How to test
There is integrations tests for this, using test containers, but to manually test.
dockerNetwork
as per kurtosis network name (usually your enclave name, eg:kt-matty-testnet
).beaconNodeAddress
as the CL node container name (eg:http://cl-1-lighthouse-nethermind--6cbd17feef8c43488af7582614edbf54:4000
). Use the containers exposed port, now we're using a custom docker network.