Hypercore rehost server: keep hypercores available
1.9K
Dockerised hypercore rehost server (https://github.com/HDegroote/hypercore-rehost-server)
It's easiest to run the Rehoster container with host networking, rather than the default bridge network, because otherwise the Hyperswarm stack struggles to Holepunch to other instances on the same LAN.
docker run -d --network host hdegroote/rehoster
If you wish to store the corestore outside of the docker, use a volume
docker run -d --network host --mount type=volume,source=rehoster-volume,destination=/home/rehoster/store hdegroote/rehoster
There is no need to expose an additional port: the DHT will holepunch into your Docker. However, if you wish to specify the port on which the DHT runs (for example if you unfirewalled a specific port), you can do so
docker run -d --network host --mount type=volume,source=rehoster-volume,destination=/home/rehoster/store --env SWARM_PORT=50000 hdegroote/rehoster
Content type
Image
Digest
sha256:df17277c9…
Size
87.6 MB
Last updated
almost 2 years ago
docker pull hdegroote/hypercore-rehost-server