Exactly the same issue here. Installed and it's running fine. I have access to the web UI and media. The library is up and running, detecting new files etc. I am even seeing clients -> LG TV, windows media player from the other pc, VLC from android device etc. The issue is that they are not seeing the server. The UDP port is mapped and used only by serviio - made sure of that. When i was having issues with this on my PC it was because i have selected the wrong ethernet device for serviio to use. When selectig the proper one - everything was fine.
Now i have the issue where i can not actually select my static ip, delegated by the router. I only see some docker networks. I have tried selecting each of those - no luck. The current setup is OMV5 (OpenMediaVault -> Debian) and serviio running in docker container.
I have tried almost everything i saw with different network modes (bridge, host, etc.). Started experimenting with macvlan configuration, but so far haven't had any success. The service is only available inside the docker.
Any suggestion would be nice.
Okay i have made it work. It's not the ideal solution yet, because it requires some manual work on restart, but it's something.
Docker-compose:
- Code:
version: '3'
services:
serviio:
image: riftbit/serviio:latest
network_mode: MacLan
dns:
- 8.8.8.8
ports:
- "23423:23423/tcp"
- "8895:8895/tcp"
- "1900:1900/udp"
volumes:
- <physical-path-on-hdd>/Config/serviio/library:/opt/serviio/library
- <physical-path-on-hdd>/Config/serviio/plugins:/opt/serviio/plugins
- <physical-path-on-hdd>/Config/serviio/log:/opt/serviio/log
- <physical-path-on-hdd>:/media/serviio
The MacLan network is newly created macvlan network, to expose the container to the lan network. This video was extremely helpful, because it's a little strange how to work with macvlan (
https://www.youtube.com/watch?v=1HCHkMV-Icc ) - first i have created the following config:
Macvlanconfig:
IPV4 Subnet - 192.168.1.0/24
IPV4 IP range - 192.168.1.150/29
IPV4 Gateway - 192.168.1.1
IPV4 Excluded Ips
After that i have created the following network to be attached to the service:
MacLan:
Driver macvlan
Scope swarm
Attachable true
Internal false
Now that i have the network i have to manually add the network to the created service, beause for some reason it does not attach on creation, even though it's set in the compose. Here it will be quite nice to have some help on how to automatically join the container/service to the network, because i haven't tested what will happen on restart.
The other small change in the composer file is specifying the DNS, beause with this macvlan network the container is requesting an IP from the router, and it's not waiting for one to be asigned with DHCP, which means there is no DNS assigned also. If you don't specify a DNS then the movies/tv series is not being fetched from whereever it needs to fetch those.
When attaching the service to the MacLan (the created macvlan network) i can see in the Serviio console > Network Settings that on eth0 i have the proper local IP assigned to the container ( in my case 192.168.1.149).
After setting the proper adapter (eth0) with the proper IP 192.168.bla.bla now Serviio advertizes itself properly in the network and all network devices (TV, Android phones, even Windows Media Player on my desktop) see the Serviio server and also can access it as any other DLNA server.
So if anyone can help me a bit with the following to make the setup self-sufficient it would be nice:
First issue: How to make the macvlan network ot get an IP from the router's DHCP with DNS?
Second issue: How to make the service to attach itself to the network ot create, so that in case of restart everything will boot properly without the need of any manual intervention?