container of arm64v8 build of 10.7.6-1 is shipping 10.7.5 server and 10.7.6 webinterface

[da-anda]

I just updated/rebuilt the container for my RPI4 (running 64bit OS) and regardless of which tag I use (arm64v8-latest, arm64v8-version-10.7.6-1) I always seem to get a likely borked container image. All logs say that it's still running Jellyfin 10.7.5, while the webinterface is listed as 10.7.6. In the admin overview, all UPNP/DLNA clients are also listed as versoin 10.7.5, which adds to my assumption that JF itself is still entirely 10.7.5 in this image. Can't tell if any other image (32, amd, ...) is also affected, but arm64v8 certainly seems to be borked. So I suspect something went wrong when the image was built?

Expected Behavior

the container image should actually contain Jellyfin 10.7.6

Current Behavior

image seems to ship wrong version of Jellyfin

Steps to Reproduce

create a new container using the image

Environment

OS: HomeAssistant OS 64 bit CPU architecture: arm64 How docker service was installed:

images is fetched from dockerhub directly

Command used to create docker container (run/create/compose/screenshot)

Docker logs

[github-actions[bot]]

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

[tobbenb]

If I remember correctly from our internal chat, 10.7.6 is the server version, but webinterface is still 10.7.5. So it's a Jellyfin issue.

[da-anda]

all logs show 10.7.5 as server version, and 10.7.6 as webinterface version. JF guys claim their image is fine and it must be a lsio issue.

To verify that I pulled the correct image, I just did a composer image list:

linuxserver/jellyfin                              arm64v8-latest             291                                                                                                                                                             60b28c31b   5 days ago      418MB
linuxserver/jellyfin                              arm64v8-version-10.7.6-1   291                                                                                                                                                             60b28c31b   5 days ago      418MB

apt list jellyfin inside the container gives me

root@local-jellyfin:/# apt list jellyfin
Listing... Done
jellyfin/now 10.7.6-1 all [installed,local]

but jellyfin log and any info screen in the web UI show 10.7.5

[2021-06-23 11:50:35.928 +02:00] [INF] [1] Main: Jellyfin version: "10.7.5"
[2021-06-23 11:50:36.020 +02:00] [INF] [1] Main: Environment Variables: ["[JELLYFIN_CONFIG_DIR, /data]", "[JELLYFIN_DATA_DIR, /data/jellyfin]", "[JELLYFIN_LOG_DIR, /share/jellyfin/log]", "[JELLYFIN_CACHE_DIR, /share/jellyfin/cache]"]
[2021-06-23 11:50:36.034 +02:00] [INF] [1] Main: Arguments: ["/usr/lib/jellyfin/bin/jellyfin.dll", "--ffmpeg=/usr/lib/jellyfin-ffmpeg/ffmpeg", "--webdir=/usr/share/jellyfin/web"]
[2021-06-23 11:50:36.040 +02:00] [INF] [1] Main: Operating system: "Linux"
[2021-06-23 11:50:36.040 +02:00] [INF] [1] Main: Architecture: Arm64
[2021-06-23 11:50:36.044 +02:00] [INF] [1] Main: 64-Bit Process: True
[2021-06-23 11:50:36.046 +02:00] [INF] [1] Main: User Interactive: True
[2021-06-23 11:50:36.046 +02:00] [INF] [1] Main: Processor count: 4

no idea. So maybe it is a JF issue with the PPA?

[Roxedus]

At the time of our build, they had different versions in their ppa.

[da-anda]

so new builds in the pipeline, or how should we go from here?

[joshuaboniface]

At the time of our build, they had different versions in their ppa.

How are you guys timing/triggering your builds? Our CI is sometimes slow.

[Roxedus]

We check each hour. With the latest commit we now ensure web, server and the jellyfin package itself is the same version, on our master branch.

[da-anda]

thanks, new image is working as expected now!