Is there an existing issue for this?
Current Behavior
I tried to start a container with v.5.1.4, with a custom env-file and behind a gluetun container, but encountered an issue where the container only spat out an error message saying: "exec /init: exec format error".
I tried changing the version to 5.1.2 and that worked. I never tried 5.1.3 because all tags had other stuff that I know nothing about. So I avoided that version.
So I'm wondering if there is an issue with 5.1.4?
Expected Behavior
Starting a container with qbittorrent shouldn't spit out an error like: "exec /init: exec format error". Especially when earlier versions doesn't appear to.
Steps To Reproduce
- run docker on a debian 13
- Start a container with lscr.io/linuxserver/qbittorrent
- inspect logs.
Environment
- OS:Debian 13
- How docker service was installed: with install script. Instuctions according to get.docker.com
CPU architecture
x86-64
Docker creation
services:
qbittorrent:
image: lscr.io/linuxserver/qbittorrent:latest
container_name: qbittorrent
restart: unless-stopped
volumes:
- ${FOLDER_FOR_DATA:?err}/qbittorrent:/config
- ${FOLDER_FOR_MEDIA:?err}:/data
environment:
- PUID=${PUID:?err}
- PGID=${PGID:?err}
- UMASK=${UMASK:?err}
- TZ=${TIMEZONE:?err}
- WEBUI_PORT=${WEBUI_PORT_QBITTORRENT:?err}
- DOCKER_MODS=ghcr.io/themepark-dev/theme.park:qbittorrent
- TP_THEME=${TP_THEME:?err}
## Do Not Change Network for qBittorrent
## qBittorrent MUST always use a VPN / Secure Internet connection
network_mode: "container:gluetun"
Container logs
exec /init: exec format error
exec /init: exec format error
exec /init: exec format error
exec /init: exec format error
Is there an existing issue for this?
Current Behavior
I tried to start a container with v.5.1.4, with a custom env-file and behind a gluetun container, but encountered an issue where the container only spat out an error message saying: "exec /init: exec format error".
I tried changing the version to 5.1.2 and that worked. I never tried 5.1.3 because all tags had other stuff that I know nothing about. So I avoided that version.
So I'm wondering if there is an issue with 5.1.4?
Expected Behavior
Starting a container with qbittorrent shouldn't spit out an error like: "exec /init: exec format error". Especially when earlier versions doesn't appear to.
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
services: qbittorrent: image: lscr.io/linuxserver/qbittorrent:latest container_name: qbittorrent restart: unless-stopped volumes: - ${FOLDER_FOR_DATA:?err}/qbittorrent:/config - ${FOLDER_FOR_MEDIA:?err}:/data environment: - PUID=${PUID:?err} - PGID=${PGID:?err} - UMASK=${UMASK:?err} - TZ=${TIMEZONE:?err} - WEBUI_PORT=${WEBUI_PORT_QBITTORRENT:?err} - DOCKER_MODS=ghcr.io/themepark-dev/theme.park:qbittorrent - TP_THEME=${TP_THEME:?err} ## Do Not Change Network for qBittorrent ## qBittorrent MUST always use a VPN / Secure Internet connection network_mode: "container:gluetun"Container logs