Docker linuxserver.io/jellyfin multiarch 207：“執行格式錯誤”

Question

我有一個問題，我不知道去哪里尋找問題。 我正在運行 debian:buster 並且我正在嘗試將其設置為 jellyfin 服務器。

我添加了必要的架構（amd64）。

user@server:~$ sudo dpkg --print-architecture
i386
user@server:~$ sudo dpkg --print-foreign-architectures
amd64
arm64

我根據 linuxserver.io/jellyfin 文檔中的示例創建了一個 docker-compose 文件。

version: "2"
services:
  jellyfin:
    image: linuxserver/jellyfin:amd64-latest
    container_name: jellyfin
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/Chicago
      - UMASK_SET=022 #optional
    volumes:
      - /srv/jellyfin/cache/
      - /srv/jellyfin/config/
      - /media/nasdisk1/series/
      - /media/nasdisk1/films/
      - /media/nasdisk2/muziek/
    ports:
      - 8096:8096
      - 8920:8920
    restart: unless-stopped

當我執行sudo docker-compose up ，容器正在嘗試重新啟動，並且容器的日志顯示：

standard_init_linux.go:207: exec user process caused "exec format error"

當我查看守護程序的日志時，它具有以下內容：

Jan  3 10:04:54 server systemd-udevd[10726]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan  3 10:04:54 server systemd-udevd[10726]: Could not generate persistent MAC address for veth27501f9: No such file or directory
Jan  3 10:04:54 server systemd-udevd[10409]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan  3 10:04:54 server systemd-udevd[10409]: Could not generate persistent MAC address for vethf2645f0: No such file or directory
Jan  3 10:04:54 server dockerd[835]: time="2021-01-03T10:04:54.762831765+01:00" level=info msg="shim docker-containerd-shim started" address=/containerd-shim/moby/aac362ac93e9e49bd98e1ae5e5677f36b7622f01467d97be972801fff6e55fa2/shim.sock debug=false pid=11392
Jan  3 10:04:54 server systemd[766]: tmp-runc.Jzl4EG.mount: Succeeded.
Jan  3 10:04:54 server systemd[1255]: tmp-runc.Jzl4EG.mount: Succeeded.
Jan  3 10:04:54 server systemd[1]: tmp-runc.Jzl4EG.mount: Succeeded.
Jan  3 10:04:55 server dockerd[835]: time="2021-01-03T10:04:55.369653723+01:00" level=info msg="shim reaped" id=aac362ac93e9e49bd98e1ae5e5677f36b7622f01467d97be972801fff6e55fa2
Jan  3 10:04:55 server dockerd[835]: time="2021-01-03T10:04:55.380208387+01:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Jan  3 10:04:55 server systemd-udevd[10726]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan  3 10:04:55 server systemd[1255]: run-docker-netns-bb13291a727b.mount: Succeeded.
Jan  3 10:04:55 server systemd[766]: run-docker-netns-bb13291a727b.mount: Succeeded.
Jan  3 10:04:55 server systemd[1]: run-docker-netns-bb13291a727b.mount: Succeeded.
Jan  3 10:04:55 server systemd[766]: var-lib-docker-containers-aac362ac93e9e49bd98e1ae5e5677f36b7622f01467d97be972801fff6e55fa2-mounts-shm.mount: Succeeded.
Jan  3 10:04:55 server systemd[1]: var-lib-docker-containers-aac362ac93e9e49bd98e1ae5e5677f36b7622f01467d97be972801fff6e55fa2-mounts-shm.mount: Succeeded.
Jan  3 10:04:55 server systemd[1255]: var-lib-docker-containers-aac362ac93e9e49bd98e1ae5e5677f36b7622f01467d97be972801fff6e55fa2-mounts-shm.mount: Succeeded.
Jan  3 10:04:55 server systemd[1]: var-lib-docker-overlay2-9fed81476b3c95a4437492d16744fe31d376aff8b329166b1e4fa6a34f6b9410-merged.mount: Succeeded.
Jan  3 10:04:55 server systemd[1255]: var-lib-docker-overlay2-9fed81476b3c95a4437492d16744fe31d376aff8b329166b1e4fa6a34f6b9410-merged.mount: Succeeded.
Jan  3 10:04:55 server systemd[766]: var-lib-docker-overlay2-9fed81476b3c95a4437492d16744fe31d376aff8b329166b1e4fa6a34f6b9410-merged.mount: Succeeded.
Jan  3 10:04:56 server avahi-daemon[610]: Interface br-d72bd039829d.IPv6 no longer relevant for mDNS.
Jan  3 10:04:56 server avahi-daemon[610]: Leaving mDNS multicast group on interface br-d72bd039829d.IPv6 with address fe80::42:eaff:fede:4bc1.
Jan  3 10:04:56 server avahi-daemon[610]: Interface br-d72bd039829d.IPv4 no longer relevant for mDNS.
Jan  3 10:04:56 server avahi-daemon[610]: Leaving mDNS multicast group on interface br-d72bd039829d.IPv4 with address 172.19.0.1.
Jan  3 10:04:56 server avahi-daemon[610]: Withdrawing address record for fe80::42:eaff:fede:4bc1 on br-d72bd039829d.
Jan  3 10:04:56 server avahi-daemon[610]: Withdrawing address record for 172.19.0.1 on br-d72bd039829d.
Jan  3 10:04:56 server dbus-daemon[598]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8' (uid=0 pid=600 comm="/usr/sbin/NetworkManager --no-daemon ")
Jan  3 10:04:56 server systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan  3 10:04:56 server dbus-daemon[598]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan  3 10:04:56 server systemd[1]: Started Network Manager Script Dispatcher Service.
Jan  3 10:04:56 server nm-dispatcher: req:1 'down' [br-d72bd039829d]: new request (1 scripts)
Jan  3 10:04:56 server nm-dispatcher: req:1 'down' [br-d72bd039829d]: start running ordered scripts...

我在網上看到有人說它與架構有關，我也看到有人建議它與 dockerfiles 中的入口點有關。 我已經嘗試過使用谷歌搜索，但我缺少有效執行此操作的必要參考框架。

這里出了什么問題？

Answer 1

我通過詢問一些聰明人找到了答案。

錯誤“執行格式錯誤”幾乎總是指不支持的架構或其他問題。

使用 dpkg 查看架構不是正確的方法。 它顯示了允許使用哪些架構安裝的軟件包。 不是主機 cpu 架構。

sudo dpkg --print-architecture
i386
user@server:~$ sudo dpkg --print-foreign-architectures
amd64
arm64

arch命令顯示主機 cpu 架構。

arch
i686

問題是 i686 是 32 位架構，而 jellyfin 和 linux 服務器只支持 64 位架構。 我偶然在我的系統上安裝了 32 位 debian 而不是 64 位。