Tvheadend

you have to run tvheadend with arguments pointing to your sat>ip server.

this is an exemple of creating docker container with arguments(running tvheadend in docker as client):

docker create \
--name=tvheadend \
-e PUID=0 \
-e PGID=0 \
-e TZ=Europe/Lisbon \
-e RUN_OPTS= --satip_xml http://ip_of_satip_server:port/satip_server/desc.xml \
-p 9981:9981 \
--device /dev/dri:/dev/dri \
--restart unless-stopped \
linuxserver/tvheadend

this will make tvheadend run manualy pointing to satip device.

or may try running docker in host mode, works here for an Fritz and DD Octopus Netv2 SatIP Device ...
if the satip is broadcasting it should be good.

How do I find the URL for my Octopus Net? Where is desc.xml located?

Daniel

the octopus should be visible automatically

Sadly, it is not. At least not under configuration DVB Inputs TV Adapters or Networks...

1. devices:
   #- /dev/dri:/dev/dri #optional
   #- /dev/drb:/dev/dvb #optional
   restart: unless-stopped

If this pseudo virtualisation can use your network, in both direction, then you can see it, else no.

I do not think that the Docker networking is fully transparent. I am no expert.

However there seems to be the option --satip_xml. Could I use that? How would I find the correct URL for the Octopus Net?

Your current Docker configuration is only opening ports 9981 and 9982 to Docker, any services that run on other ports are not accessible to the host. Consider using "--network host" rather than "- 9981:9981" and "- 9982:9982". Be warned if you are running TVH on a Docker instance with other applications this may have unintended consequences.

Thanks, that did indeed work. This way I found the correct URL for satip_xml (http://ip/octoserve/octonet.xml). I am now using this address.