Container is binding to incorrect subnet and ignoring network.xml

[ghostkjb]

Output still binding to 192.168.0.0/16:

Jellyfin is not binding to any specific address.  19.168.0.0/16 in this context is defining what is considered "internal".  There is a separate config for binding.

From your log

[18:59:28] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Using bind addresses: []
[18:59:28] [INF] [1] Jellyfin.Networking.Manager.NetworkManager: Using bind exclusions: []

These lines being blank indicates it is binding to all available interfaces.

Q: When you said you tried to access it via "localhost:8096", is that from the HOST running the VM?  Or from within the VM?
A: The host running the vm. From Firefox on the VM that is the host running docker running the Jellyfin container - I cannot reach localhost:8096

If you are accessing localhost from within the VM it should allow it. If you are accessing it from the HOST running the VM, it would be blocked by the firewall if you didn't create a rule.

If this is a debian based distro, you should have UFW either pre-installed or available in the repo.

Code:

sudo ufw enable
sudo ufw allow 8096

If you are accessing localhost from within the VM it should allow it. If you are accessing it from the HOST running the VM, it would be blocked by the firewall if you didn't create a rule.
I am accessing it within the Ubuntu server VM, just not within the docker container its self. I still enabled ufw and allowed 8096 on the Ubuntu Server VM running Docker, but I still can't access localhost:8086 on the vm.

Should we turn off "ignore virtual interfaces"?