[BUG] transmission-remote is missing in 4.0.3-r2-ls174

[ioqy]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current Behavior

transmission-remote is missing from the container image

Expected Behavior

No response

Steps To Reproduce

Execute docker exec transmission transmission-remote with the version 4.0.3-r2-ls174 gives the following output:

OCI runtime exec failed: exec failed: unable to start container process: exec: "transmission-remote": executable file not found in $PATH: unknown

Using the previous version 4.0.3-r1-ls173 executes transmission-remote inside the container. I also searched inside the container but couldn't find transmission-remote anywhere.

Environment

- OS: Debian 11
- How docker service was installed: distro's packagemanager

CPU architecture

x86-64

Docker creation

version: "2.1"
services:
  transmission:
    image: lscr.io/linuxserver/transmission:4.0.3-r2-ls174
    container_name: transmission
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=<redacted>
      - USER=<redacted>
      - PASS=<redacted>
    volumes:
      - /srv/transmission/transmission:/config
    healthcheck:
      disable: true
    depends_on:
      - gluetun
    network_mode: service:gluetun
    restart: unless-stopped

Container logs

[migrations] started
[migrations] no migrations found
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────

[custom-init] No custom files found, skipping...
[ls.io-init] done.

[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.