</code></pre><h3id=docker-cli-click-here-for-more-info>docker cli (<ahref=https://docs.docker.com/engine/reference/commandline/cli/>click here for more info</a>)</h3><pre><codeclass=language-bash>docker run -d \
--name=domoticz \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Europe/London \
-e WEBROOT=domoticz `#optional` \
-e DBASE=<path to database> `#optional` \
-p 8080:8080 \
-p 6144:6144 \
-p 1443:1443 \
-v <path to data>:/config \
--device path to device:path to device \
--restart unless-stopped \
lscr.io/linuxserver/domoticz:latest
</code></pre><h3id=passing-through-usb-devices>Passing Through USB Devices</h3><p>To get full use of Domoticz, you probably have a USB device you want to pass through. To figure out which device to pass through, you have to connect the device and look in dmesg for the device node created. Issue the command 'dmesg | tail' after you connected your device and you should see something like below.</p><pre><code>usb 1-1.2: new full-speed USB device number 7 using ehci-pci
ftdi_sio 1-1.2:1.0: FTDI USB Serial Device converter detected
usb 1-1.2: Detected FT232RL
usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0
</code></pre><p>As you can see above, the device node created is ttyUSB0. It does not say where, but it's almost always in /dev/. The correct tag for passing through this USB device is '--device /dev/ttyUSB0:/dev/ttyUSB0'</p><h2id=parameters>Parameters</h2><p>Docker images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <code><external>:<internal></code> respectively. For example, <code>-p 8080:80</code> would expose port <code>80</code> from inside the container to be accessible from the host's IP on port <code>8080</code> outside the container.</p><h3id=ports-p>Ports (<code>-p</code>)</h3><table><thead><tr><thalign=center>Parameter</th><th>Function</th></tr></thead><tbody><tr><tdalign=center><code>8080</code></td><td>WebUI</td></tr><tr><tdalign=center><code>6144</code></td><td>Domoticz communication port.</td></tr><tr><tdalign=center><code>1443</code></td><td>Domoticz communication port.</td></tr></tbody></table><h3id=environment-variables-e>Environment Variables (<code>-e</code>)</h3><table><thead><tr><thalign=center>Env</th><th>Function</th></tr></thead><tbody><tr><tdalign=center><code>PUID=1000</code></td><td>for UserID - see below for explanation</td></tr><tr><tdalign=center><code>PGID=1000</code></td><td>for GroupID - see below for explanation</td></tr><tr><tdalign=center><code>TZ=Europe/London</code></td><td>Specify a timezone to use EG Europe/London.</td></tr><tr><tdalign=center><code>WEBROOT=domoticz</code></td><td>Sets webroot to domoticz for usage with subfolder reverse proxy. Not needed unless reverse proxying.</td></tr><tr><tdalign=center><code>DBASE=<path to database></code></td><td>Sets path to database. Do not set unless you know what this does.</td></tr></tbody></table><h3id=volume-mappings-v>Volume Mappings (<code>-v</code>)</h3><table><thead><tr><thalign=center>Volume</th><th>Function</th></tr></thead><tbody><tr><tdalign=center><code>/config</code></td><td>Where Domoticz stores config files and data.</td></tr></tbody></table><h3id=device-mappings-device>Device Mappings (<code>--device</code>)</h3><table><thead><tr><thalign=center>Parameter</th><th>Function</th></tr></thead><tbody><tr><tdalign=center><code>path to device</code></td><td>For passing through USB devices.</td></tr></tbody></table><h4id=miscellaneous-options>Miscellaneous Options</h4><table><thead><tr><thalign=center>Parameter</th><th>Function</th></tr></thead><tbody><tr><td></td><td></td></tr></tbody></table><h2id=environment-variables-from-files-docker-secrets>Environment variables from files (Docker secrets)</h2><p>You can set any environment variable from a file by using a special prepend <code>FILE__</code>.</p><p>As an example:</p><pre><codeclass=language-bash>-e FILE__PASSWORD=/run/secrets/mysecretpassword
</code></pre><p>Will set the environment variable <code>PASSWORD</code> based on the contents of the <code>/run/secrets/mysecretpassword</code> file.</p><h2id=umask-for-running-applications>Umask for running applications</h2><p>For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional <code>-e UMASK=022</code> setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up <ahref=https://en.wikipedia.org/wiki/Umask>here</a> before asking for support.</p><h2id=user-group-identifiers>User / Group Identifiers</h2><p>When using volumes (<code>-v</code> flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user <code>PUID</code> and group <code>PGID</code>.</p><p>Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.</p><p>In this instance <code>PUID=1000</code> and <code>PGID=1000</code>, to find yours use <code>id user</code> as below:</p><pre><codeclass=language-bash> $ id username
</code></pre><h2id=docker-mods>Docker Mods</h2><p><ahref="https://mods.linuxserver.io/?mod=domoticz"title="view available mods for this container."><imgalt="Docker Mods"src="https://img.shields.io/badge/dynamic/yaml?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=domoticz&query=%24.mods%5B%27domoticz%27%5D.mod_count&url=https%3A%2F%2Fraw.githubusercontent.com%2Flinuxserver%2Fdocker-mods%2Fmaster%2Fmod-list.yml"></a><ahref="https://mods.linuxserver.io/?mod=universal"title="view available universal mods."><imgalt="Docker Universal Mods"src="https://img.shields.io/badge/dynamic/yaml?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=universal&query=%24.mods%5B%27universal%27%5D.mod_count&url=https%3A%2F%2Fraw.githubusercontent.com%2Flinuxserver%2Fdocker-mods%2Fmaster%2Fmod-list.yml"></a></p><p>We publish various <ahref=https://github.com/linuxserver/docker-mods>Docker Mods</a> to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.</p><h2id=support-info>Support Info</h2><ul><li>Shell access whilst the container is running:</li><li><code>docker exec -it domoticz /bin/bash</code></li><li>To monitor the logs of the container in realtime:</li><li><code>docker logs -f domoticz</code></li><li>Container version number</li><li><code>docker inspect -f '{{ index .Config.Labels "build_version" }}' domoticz</code></li><li>Image version number</li><li><code>docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/domoticz:latest</code></li></ul><h2id=versions>Versions</h2><ul><li><strong>15.10.22:</strong> - Remove deprecated legacy stable branches.</li><li><strong>05.02.22:</strong> - Set default webroot to /. Add env. variable for setting custom databas path.</li><li><strong>26.12.20:</strong> - Rebase to Ubuntu Focal, see <ahref=https://docs.linuxserver.io/faq#my-host-is-incompatible-with-images-based-on-ubuntu-focal>here</a> for troubleshooting armhf.</li><li><strong>24.11.19:</strong> - Change to using domoticz builtin Lua and MQTT.</li><li><strong>03.11.19:</strong> - Set capabilities for domoticz binary and move cmake from edge repo.</li><li><strong>28.06.19:</strong> - Rebasing to alpine 3.10. Add iputils for ping. Fix typo in readme. Fix permissions for custom icons.</li><li><strong>12.05.19:</strong> - Add boost dependencies and turn off static boost build. Bump to Alpine 3.9.</li><li><strong>30.03.19:</strong> - Add env variable to set webroot.</li><li><strong>23.03.19:</strong> - Switching to new Base images, shift to arm32v7 tag.</li><li><strong>19.02.19:</strong> - Fix branch for version logic.</li><li><strong>11.02.19:</strong> - Add pipeline logic and multi arch.</li><li><strong>02.07.18:</strong> - Add openssh package.</li><li><strong>01.07.18:</strong> - Fix backup/restore in webgui.</li><li><strong>03.04.18:</strong> - Add dependencies for BroadlinkRM2 plugin.</li><li><strong>20.01.18:</strong> - Move telldus core to repo to prevent build fail when source site goes down.</li><li><strong>18.01.18:</strong> - Remove logging to syslog in the run command to prevent double logging.</li><li><strong>04.01.18:</strong> - Deprecate cpu_core routine lack of scaling.</li><li><strong>08.12.17:</strong> - Rebase to alpine 3.7.</li><li><strong>26.11.17:</strong> - Use cpu core counting routine to speed up build time.</li><li><strong>28.05.17:</strong> - Rebase to alpine 3.6.</li><li><strong>26.02.17:</strong> - Add curl and replace openssl with libressl.</li><li><strong>11.02.17:</strong> - Update README.</li><li><strong>03.01.17:</strong> - Initial Release.</li></ul></article></div></div></main><footerclass=md-footer><navclass="md-footer__inner md-grid"aria-label=Footer><ahref=../docker-dokuwiki/class="md-footer__link md-footer__link--prev"aria-label="Previous: dokuwiki"rel=prev><divclass="md-footer__button md-icon"><sv
