Docker image for byteball-hub
The simplest way to create the docker image and run byteball-hub is below.
$ docker build -t byteball-hub .
$ docker run -d byteball-hubalthough it is always a good idea to give a container a name you can remember:
$ docker run -d --name my-byteball-hub byteball-hubTo stop the container and then restart it again, use:
$ docker stop my-byteball-hub
$ docker start my-byteball-hubAlthough the byteball-hub docker image has been set up to create a volume and store the byteball runtime files on the host filesystem, using a named volume is recommended so containers can be dropped and recreated easily by referencing the existing storage by a simple name:
$ docker volume create --name byteball-hub
$ docker run -d --name my-byteball-hub -v byteball-hub:/byteball byteball-hubNOTE: The configuration files are stored in the /byteball folder inside the container.
In order to change the configuration file, stop the byteball-hub container and start a new one like below:
$ docker run -it --rm -v byteball-hub:/byteball byteball-hub vi /byteball/conf.jsonThis will mount the named byteball volume and open/create the conf.json file in the
vi text editor. When you quit from vi the container will automatically
delete itself due to the --rm flag.
Now you can start the container again and the app will start up with the changed configuration.
See configuration options here:
In case you need to check the log files you can use the following command:
$ docker run -it --rm -v byteball-hub:/byteball byteball-hub less /byteball/log.txtIf you enabled the default websocket port (6611) you may want to map it a port on your host system. You have to create the container as below, but you may first want to stop and remove the running container before creating a new one.
$ docker stop my-byteball-hub
$ docker rm my-byteball-hub
$ docker run -d --name my-byteball-hub -v byteball-hub:/byteball -p 6611:6611 byteball-hubThis will map the 6611 port of the host system to the 6611 port of the container.