Quick update: I’ve released a new version with some improvements, features, better error handling and hopefully a better description how to use it.
The main change is extra validation of the provided configuration against the actual network settings inside the container. This should lead to clearer errors when the details don’t align correctly.
The improved docs should make things clearer, here is an excerpt:
Running the Testnet
Getting this testnet container running smoothly, especially connecting your clients to it, means thinking a bit about networking. The services inside the container (the Autonomi nodes, the EVM, the bootstrap server) need to be directly reachable by your client applications running outside the container, usually on the same local network.
There’s a check built into the container startup: the
EXTERNAL_IP_ADDRESSyou set must be an IP address that the container itself actually has access to on one of its network interfaces. This is a bit unusual for a container! It means typical setups where Docker gives the container a private, internal-only IP won’t work properly and the container won’t start. You need a network setup where the container gets an IP reachable from your clients. The easiest way to handle this is using--network host, which makes the container share your hosts’s network address directly.
The new feature is ANTNODE_SOURCE:
Controls which
antnodebinary is used. Set toLATESTto download the most recent version on startup, or any other value to use the version bundled within the Docker image.