Sonos in Docker

Lolodomo · December 25, 2023, 10:01am

Fine.
Could you please contribute by an enhancement of the following page in documentation ?

The corresponding page in Github to propose your change :

openhab/openhab-docs/blob/main/installation/docker.md

---
layout: documentation
title: Docker
---

# openHAB inside a Docker Container

Docker is the most popular among a collection of tools that provide containerization.
Containerization allows one to run a server in its own isolated environment without the overhead of running a full virtual machine.

This page is structured as follows:

[[toc]]

## Why Docker?

There are several reasons one would want to run openHAB in a Docker container.
These include:

- easily test out different versions

This file has been truncated. show original

patrik_gfeller · December 26, 2023, 12:38pm

@Franco

Let me know if you plan to update the readme. Else I could do it as well - as I consider it very valuable information. But it does not make sense if I do something that will conflict with your work.

Franco · December 26, 2023, 12:45pm

If you can that would be great as im quite busy with my kids these days.

patrik_gfeller · December 26, 2023, 5:23pm

fyi: I’ve updated

github.com/openhab/openhab-addons

[sonos] Multiple docker networks interfere with binding

opened 03:23PM - 04 Jul 22 UTC

arins

enhancement documentation

If i have multiple docker containers running with ports exposed besides openhab …docker container this causes the sonos binding give error UPnP/DLNA binding: UPnP device not yet registered. I can also let you know that I don't have any special network settings. I run everything under 192.168.1.x network. Sonos and OH3 is under same subnet. ## Expected Behavior sonos binding should just work even though I have other containers running side by side with openhab docker container ## Current Behavior When I have other docker containers with network_mode: host there is no issue but when exposing ports and not using network_mode: host this error appears: **UPnP/DLNA binding: UPnP device not yet registered.** This causes the sonos things to be offline. ## Possible Solution If I use network_mode: host on all other docker containers and delete all networks in docker then sonos binding starts working and all sonos things becomes online. ## Steps to Reproduce (for Bugs) 1. Run OH3 in docker 2. Run other services with exposes ports on the same machine. (tested on both rasberry pi 4 and a intel machine.) 3. Sonos things becomes offline (sometimes some sonos things and sometimes all of them.) ## Context I can not use the sonos binding. I was thinking using node-red because there it works fine! Maybe check if sonos binding get inteference when docker creates a lot of networks? ## Your Environment Raspberry pi 4 with official openhab 3 docker image.

removed bug tag and added documentation and enhancement tags - as it is not a bug in the sonos binding or OH code in general.

I think that once the doc is updated that issue can be closed.

arins · December 26, 2023, 5:29pm

I am going to test this evening. I think it will work when jupnp network interface is specified

patrik_gfeller · December 27, 2023, 10:46pm

A preview of the updated documentation is available at Installation - Docker.

At all:
Please feel free to comment on the PR and provide suggestions if changes are required. If you have feedback, please be as precise as possible - so that I know what you would like to change, or even directly use the text.

It would also be appreciated if a user running docker on a windows system could help me out to create the respective tab in the docu on how to find the correct interface name.

pgruetter · December 28, 2023, 9:15am

Thanks a lot! Found a typo, added a comment on the PR.
A few additional points:

I actually added a second parameter in my config: -Dorg.jupnp.network.useAddresses=192.168.X.X. I’m not sure if this is necessary, maybe someone can confirm.
The [^multicastrouting] is rendered as is, not sure what the intention is here?
Since the problem was primarily discussed with the SONOS binding (I think…), maybe it’s worth adding a link to this docker page in the corresponding binding documentation?

patrik_gfeller · December 28, 2023, 10:56am

Thanks for the feedback

I use this parameter as well - I’ll try if it works without, else I’ll add it to the documentation as well.

That should actually be a footnote - but did not notice that the used markdown renderer does not support this syntax extension. I’ll fix this.

Unsure about this one … let’s see if we get other feedback on that - of course it is somewhat related - but not exactly part of the binding configuration. I’ll wait for some more opinions/votes on that one. If desired I will add such a link to the SONOS binding docu.

Lolodomo · December 28, 2023, 12:34pm

Users using docker will normally read the page dedicated to docker installation.
We have many bindings relying upon UPnP. I am really not sure we should add a specific docker link in the documentation of each of them.

pgruetter · December 28, 2023, 1:01pm

OK, I see your points, so let’s focus on the Docker page.

rlkoshak · December 28, 2023, 5:49pm

Note, this behavior might be a regression. See Openhab 4.1 starts mass of SocketListener and JmDNS Threads in Docker · Issue #3976 · openhab/openhab-core · GitHub. Updates to the docs may not be what’s needed here. It might be a bug. OH is supposed to use the network you configured in Settings → Network as the primary for UPnP stuff.

patrik_gfeller · December 28, 2023, 7:42pm

thanks for the reference!

I’m using OH 4.1.0 - and it seems to respect the parameters. I’ve updated the info in the issue you reference together with the settings I use (including settings for the logger to debug the issue). It might make sense, that UPnP only binds to the interface specified in the UI - but I can not comment if there are scenarios when it makes sense to bind to several networks and/or control them …

Anyhow - the java option approach seems to work - at least in my setup. Let see what the logs will show for @scriptwriter13’s setup. I noticed that the setting is quite sensitive on how quotation marks - had problems with that at the beginning.

The other thing is, that my setup (configuration/data) has been migrated - it is not a new install. Not sure if a clean 4.1.0 install will behave differently.

I’ll wait for the results of the log; depending on the result I’ll create a clean/new 4.1.0 container with default settings and my .env file to see if this works or not.

Scriptwriter · December 29, 2023, 10:11am

HI @patrik_gfeller, @pgruetter , @Lolodomo , @wborn and all others,

other projects like apache or any other serverproject has possibility that you really can define one or multiple listener-interfaces or * for all interfaces.

In Openhab there is a possibility to select under network-settings an ip address. But this does not work in openhab in this way as the listener-config on other server-software.

All problems on docker like UPNP and the multiple instances on all interfaces, mine with the SocketListener and JmDNS, this one with the Pings on docker (another issue i opened in github under addons) would not exist if it would be possible to bind openhab to only one interface. So from my guessings it should be thought about that to make this possible to make life of docker-openhab-users easier.

wborn · December 29, 2023, 11:18am

You can already restrict functionality to interfaces in the Network Configuration settings however these settings aren’t used by all Core and add-ons code.

I can also imagine there are users with setups where using only one interface breaks functionality and using all interfaces causes performance issues. In that case they may want to be able to configure multiple interfaces. For example if you want to ping hosts on the Internet, in your local network and Docker containers on the same host.