SOLVED: Connection refused on NAS after upgrading to 10.9.xx from 10.8.13

[AGiLiT]

I just tried upgrading Jellyfin on my WD NAS from 10.8.13 to 10.9.10, running in a docker container.  I get a connection refused message when I try to access x.x.x.x:8096.  I can't telnet to the port either (I reinstalled 10.8.13 and verified telnet connection works on that version.

I always build my containers via. a Putty connection to the NAS and using docker run command.  Using portainer on the NAS to look at container logs and info, I see that 10.9 version shows container status as unhealthy, and logs show error message, 'Failed to create core CLR'.

I hope that's enough of a starting point to guide me on what I should look at next to try and resolve this.

Thanks.

[TheDreadPirate]

Is the container actually running? Unhealthy can be due to use of host networking.

Can you share the jellyfin logs via pastebin?

[AGiLiT]

Is the container actually running?  Unhealthy can be due to use of host networking.

Can you share the jellyfin logs via pastebin?

The log files are empty (I deleted old ones before rebuilding the new container.)

Here is the output of a docker ps command:

root@Our-Cloud1 ~ # docker ps
CONTAINER ID  IMAGE                                          COMMAND                CREATED        STATUS                            PORTS                                                      NAMES
122dd5965be7  jellyfin/jellyfin:latest                        "/jellyfin/jellyfin"  7 minutes ago  Restarting (137) 37 seconds ago                                                              wizardly_williams

[AGiLiT]

Fixed it!  Thank you Google.  Googling 'Failed to create coreclr in docker container' led me to discussions about upgrades in .Net and docker versions.  WD doesn't support docker natively, so we have to rely on the community to provide .bin files to install it.  There aren't any really current versions that I could find.  However, one of the posters in one of the threads I looked at provided this solution:

add argument --security-opt seccomp=unconfined for docker run command.

That fixed it for me, and Jellyfin is now up and running on my NAS.

Thanks again for the help.