my apologies - had submitted this last night before bed (who knows, maybe it would start working. it didnt)
My PC static IP is 192.168.1.71. Its entirely possible that we were overlooking things due to sleep so if you notice an issue then it absolutely could be something as simple as an IP conflict.
If I remove those ports mentioned in the compose, from it - the container is made and starts but doesnt run on any ports (literally the section under the container that would show the ports is blank). If I leave them in then it runs on the ports but says " jellyfin Published ports are discarded when using host network mode" so they seem to be discarded and thus shouldn't make a difference.
What I am assuming is happening is that there is an IP conflict (like you mentioned) and its starting on that, then discarding the ports related to my actual IP
localhost:8096 doesn't load either (even clicking on them in docker doesn't load it) so yeah looks like the wrong IP could def be being configured
My PC static IP is 192.168.1.71. Its entirely possible that we were overlooking things due to sleep so if you notice an issue then it absolutely could be something as simple as an IP conflict.
If I remove those ports mentioned in the compose, from it - the container is made and starts but doesnt run on any ports (literally the section under the container that would show the ports is blank). If I leave them in then it runs on the ports but says " jellyfin Published ports are discarded when using host network mode" so they seem to be discarded and thus shouldn't make a difference.
What I am assuming is happening is that there is an IP conflict (like you mentioned) and its starting on that, then discarding the ports related to my actual IP
localhost:8096 doesn't load either (even clicking on them in docker doesn't load it) so yeah looks like the wrong IP could def be being configured