nils/ebusd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

updated with multi arch info

Browse Source
This commit is contained in:
John
2021-01-17 19:29:53 +01:00
parent 385f4e2abd
commit e9c631e9e3
1 changed files with 16 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
contrib/docker/README.md
+16 -4
View File
@@ -12,9 +12,18 @@ work well on a Synology Diskstation as well as Windows with Docker Desktop.
Getting the image
-----------------
To download the latest image from the hub, use the following command:
To download the latest release image from the hub, use the following command:
> docker pull john30/ebusd
The image is able to run on any of the following architectures and the right image will be picked automatically:
* amd64
* arm32v7
In addition to the default "latest" tag, a development set of images is available with "devel" tag. This is built
automatically with every commit to the git repository. Run the following command to use it:
> docker pull john30/ebusd:devel
Running interactively
---------------------
@@ -40,13 +49,16 @@ In order to get the log output from ebusd, use the following command:
Using a network device
----------------------
When using a network device, the "--device" argument to docker can be omitted, but the device information has to be passed on to ebusd:
When using a network device, the "--device" argument to docker can be omitted, but the device information has to be
passed on to ebusd:
> docker run --rm -it -p 8888 john30/ebusd -f --scanconfig -d udp:192.168.178.123:10000 --latency=80
Note: the "-f" and "--scanconfig" arguments are only passed to ebusd if it is called without any additional arguments. So when passing further arguments, these two usually need to be added as well.
Note: the "-f" and "--scanconfig" arguments are only passed to ebusd if it is called without any additional arguments.
So when passing further arguments, these two usually need to be added as well.
Running with MQTT broker
------------------------
To start an ebusd container in the background and have it connect to your MQTT broker, use the following command while replacing "BROKERHOST" with your MQTT broker host name or IP address:
To start an ebusd container in the background and have it connect to your MQTT broker, use the following command while
replacing "BROKERHOST" with your MQTT broker host name or IP address:
> docker run -d --name=ebusd --device=/dev/ttyUSB0 -p 8888 john30/ebusd -f --scanconfig -d /dev/ttyUSB0 --mqttport=1883 --mqtthost=BROKERHOST