[Issue]: Docker network_mode: "host" binding problem #11557
Labels
bug
Something isn't working
Projects
Comments
|
Hi, it seems like your issue report has the following item(s) that need to be addressed:
This is an automated message, currently under testing. Please file an issue here if you encounter any problems. |
|
Port netstat -tulpn | grep 8096returns nothing |
|
docker compose container with host, same problem since the update: |
|
If I do not use services:
jellyfin:
volumes:
- '/home/jellyfin/config:/config'
- '/home/jellyfin/cache:/cache'
- '/home/media:/media'
ports:
- xxx.xxx.xxx.xxx:8920:8920/tcp
- xxx.xxx.xxx.xxx:8096:8096/tcp
tmpfs:
- /transcode
environment:
- TZ=Europe/Berlin
image: 'jellyfin/jellyfin:latest'
restart: "always" |
jumoog
changed the title
|
Setting |
|
It seems like you have two interfaces have the same IP.... interesting |
I've noticed that I have the same IP address twice in the log. I have this on all my servers. I have tailscale with subnet routes. I'll install a new Server without tailscale for testing. |
|
I got the same error on my unraid Docker setup. After some digging I got 2 interfaces with the same address background: https://forums.unraid.net/topic/90688-shim-br0-networs-in-unraid/?do=findComment&comment=842950 maybe this helps |
|
I also have a shim for docker<->host networking. |
|
|
I fixed the shim thing by add the interface name to the VirtualInterfaceNames ...
<IgnoreVirtualInterfaces>true</IgnoreVirtualInterfaces>
<VirtualInterfaceNames>
<string>veth</string>
<string>shim-br0</string>
</VirtualInterfaceNames>
...now my Jellyfin works again. |
|
confirming @chi110r |
|
similar problem for me: |
|
@spupuz If you can compile it yourself, you can use my dirty hack https://github.com/jumoog/jellyfin/commit/9c8d42660dade818bc3d3cdd347fa6a250087cf5 as a temporary workaround. |
|
I don't have duplicated ip |
|
@spupuz do you have anything else using the 8096 port? |
no, and if i start jellyfin docker without config as fresh it works without any problem, but i want to retain my configuration if possible. |
|
I had this issue as well when migrating to 10.9 my solution was just to switch to bridge and declare my port directly No need to really get in and rebuild from source, just mod your docker to remove net-admin. |
Did you check if you have any incompatible plugins? |
|
"address already in use" problem. It was working fine before upgrading to 10.9.0. After being automatically upgraded to 10.9.0 by Watchtower it won't start. OS: unRAID Log: network.xml None returned by Is it possible that Jellyfin binds itself to the same port twice during startup? |
This was referenced May 13, 2024
Merged
|
The original issue about having multiple interfaces sharing same IP is going to be resolved by #11587. If you don't have interfaces sharing the same IP, then you are affected by a different issue and please file a new one with complete log and environment info so we can look at it. |
|
Your fix is working! Thank you very much! |
|
@libook your logs shows 192.168.50.49 twice: Maybe netstat does not shows up jellyfin port because jellyfin stop before you check it's port. |
@prahal Hi，thanks for your view. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please describe your bug
I have pulled the new version of the docker image and Jellyfin starts with an binding error message.
Reproduction Steps
My Docker Compose file that worked in 10.8.x
Even if I change the port numbers in
network.xmlI still get the same message.Jellyfin Version
10.9.0
if other:
No response
Environment
- Virtualization: DockerJellyfin logs
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: