Cjdns docker container with Debian base.
Complexity is the enemy of security. This containers aim will be to attempt to reduce/eliminate any impact that this appliance will have on its host, while also reducing the initial learning curve required to get started. You also have the added benefit of having
a no cost learning experience meaning this will not break your host machine in the process of you learning how to use it.
This container will also not only help you learn how to get going, it will also aim to be capable of being run in container services such as Amazon's EC2 Container service. Its not intended necessarily to be run at home but to actually be run as a point of presence in a public datacenter which can give you a dedicated external access point to Hyperboria or any other meshnets.
Installation and Operation
Generate yourself some configs
docker run -ti --volume $(pwd)/cjdns:/etc/cjdns --name debian-cjdns chamunks/debian-cjdns
This will create cjdns config files in a directory named cjdns nested inside of your current working directory.
You can then modify these config files to your liking. This includes modifying the port you wish to bind cjdns to inside of your container.
Once you've done this you'll want to remove the old container and start a new one with docker run again.
docker run -d -P hostPort:containerPort --name debian-cjdns chamunks/debian-cjdns
The Old Method
Installation is simple. On first run, cjdns will generate your IP
address. The cjdns configuration lies in
/etc/cjdns (which is a
To be useful you'll have to run this in privileged mode, with the
same network stack as the host. This can be accomplished using the
docker pull mildred/cjdns docker run --privileged --net=host mildred/cjdns --volume /etc/cjdns:/etc/cjdns