[BUG] Container fails to start on Arm64

[somu1795]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current Behavior

The container fails to start with the following error: exec /init: exec format error

Expected Behavior

Container should launch normally

Steps To Reproduce

My Device: NanoPi R6C

pi@nanopi ~> sudo dpkg --print-architecture
arm64  

pi@nanopi ~> cat /etc/*release*
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

I'm able to run other docker container without any issue. I'm launching the container via docker compose in Portainer

Environment

- OS: Ubuntu 22.04
- How docker service was installed:

CPU architecture

arm64

Docker creation

version: '3.5'
services:
  jellyfin:
    image: lscr.io/linuxserver/jellyfin:latest
    container_name: jellyfin
    network_mode: 'host'

    volumes:
      - config:/config
      - cache:/cache
      - /mnt/nvme/jellyfin_media/Movies:/movies
      - /mnt/nvme/jellyfin_media/Shows:/shows
    devices: 
      - /dev/dri/renderD128:/dev/dri/renderD128
      - /dev/dri/card0:/dev/dri/card0

    restart: 'unless-stopped'
    # Optional - may be necessary for docker healthcheck to pass if running in host network mode
    extra_hosts:
      - "host.docker.internal:host-gateway"

volumes:
  config:
  cache:

### Container logs

```bash
exec /init: exec format error

[github-actions[bot]]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[somu1795]

Please re-open this issue

[j0nnymoe]

Issue was never closed. Have you tried setting the arm64v8 tag?

Note we also don't recommend/ support portainer for deployment.

[homerr]

Going to close this off as it's doubtful this is an error in the container as there are no other reports. That said, please try a manual docker-compose.yml away from Portainer and using the tag that moe suggested.

If you're still having no success please join us in Discord.