Unable to update to version 4.7.14.0 in docker via Portainer

[rjwill10 2]

I'm running Emby on a Raspberry Pi via OMV5 and Docker.

My container was built using the following docker compose:

version: "2.1"
services:
  emby:
    image: lscr.io/linuxserver/emby:latest
    container_name: emby

Emby is running as expected, but when accessing the server dashboard, I'm prompted to update from v 4.7.11.0 to 4.7.14.0.

I've tried various methods of updating. I tried to update via Yatch (after stopping the container) and also re deploying the stack and nothing seems to work?

My system details are below:

 

2023-12-30 15:58:12.782 Info Main: Application path: /app/emby/EmbyServer.dll
2023-12-30 15:58:13.373 Info Main: Emby
Command line: /app/emby/EmbyServer.dll -programdata /config -ffdetect /app/emby/ffdetect -ffmpeg /app/emby/ffmpeg -ffprobe /app/emby/ffprobe -restartexitcode 3
Operating system: Linux version 6.1.21-v8+ (dom@buildbot) (aarch64-linux-gnu-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1642 SM
Framework: .NET 6.0.8
OS/Process: arm/arm
Runtime: app/emby/System.Private.CoreLib.dll

 

Should I be able to update?

[Luke 37067]

HI, what exactly happens when you try to update? 

Also why not use our official docker container? 

https://emby.media/docker-server.html

This is what we're actively testing.

[rjwill10 2]

41 minutes ago, Luke said:

HI, what exactly happens when you try to update? 

Also why not use our official docker container? 

https://emby.media/docker-server.html

This is what we're actively testing.

Nothing happens really. In Yacht, the update is shown as available. Then I update and restart the container and it's the same version, and Yacht will show the update once again.

I did try to use the following docker compose:

version: "2.3"
services:
  emby:
    image: emby/embyserver
    container_name: embyserver
    runtime: nvidia # Expose NVIDIA GPUs
    network_mode: host # Enable DLNA and Wake-on-Lan
    environment:
      - UID=1000 # The UID to run emby as (default: 2)
      - GID=100 # The GID to run emby as (default 2)
      - GIDLIST=100 # A comma-separated list of additional GIDs to run emby as (default: 2)
    volumes:
      - /path/to/programdata:/config # Configuration directory
      - /path/to/tvshows:/mnt/share1 # Media directory
      - /path/to/movies:/mnt/share2 # Media directory
    ports:
      - 8096:8096 # HTTP port
      - 8920:8920 # HTTPS port
    devices:
      - /dev/dri:/dev/dri # VAAPI/NVDEC/NVENC render nodes
      - /dev/vchiq:/dev/vchiq # MMAL/OMX on Raspberry Pi
    restart: on-failure

but it kept giving the following error:
 

exec /init: exec format error

I also just tried to create the container with the previous console code, but using the emby/embyserver pull as follows, but kept getting the same error:
 

version: "2.1"
services:
  emby:
    image: emby/embyserver
    container_name: emby
    environment:
      - PUID=998
      - PGID=100
      - TZ=Europe/London
...
   	
    devices:
      - /dev/dri:/dev/dri #optional
      - /dev/vchiq:/dev/vchiq #optional
      - /dev/video10:/dev/video10 #optional
      - /dev/video11:/dev/video11 #optional
      - /dev/video12:/dev/video12 #optional
    ports:
      - 8096:8096
      - 8920:8920 #optional
    restart: unless-stopped

The container runs without issue, but the IP address and published ports keep dropping. I've tried both host and bridge network modes. If no mode is specified, it creates its own.

[Luke 37067]

Why do you think they’re dropping?

[rjwill10 2]

1 hour ago, Luke said:

Why do you think they’re dropping?

Unsure, but it's likely something simple that I'm missing. I noticed I was pulling the wrong emby version, so updated to pull:

emby/embyserver_arm64v8

It felt like it could be a cache issue, but I was able to clear all the config files and start fresh, and am still getting the issue, so am at a loss.

[Luke 37067]

HI, did you figure out how to update it?

[rjwill10 2]

3 hours ago, Luke said:

HI, did you figure out how to update it?

Not yet, I decided it was time to update to OMV6, and that caused a few issues that I needed to resolve first. Hoping that updating the system will resolve the install problem, as I was getting the same error when trying to install the Unifi Controller in Docker. 

I'll let you know if this resolves the issue. 

[rjwill10 2]

13 hours ago, Luke said:

HI, did you figure out how to update it?

Figured it out...I was deploying the wrong image. 

I'm running my PI on the lite 32bit image, not 64. I wrongly assumed that the emby/embyserver pull would automatically pull the right image. I then wrongly tried to pull the 64bit image which gave the same error. 

When I was pulling the lscr.io/linuxserver/emby:latest image, it was pulling the correct image.