[BUG] Command Options not working

[Salvora]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

As per the lazylibrarian docs, there are these command line options
https://lazylibrarian.gitlab.io/config_commandline/

I am trying to run the lazylibrarian on a different port with --port command using the "command" in my compose

Expected Behavior

command line options should pass to the app

Steps To Reproduce

1. Deploy the below compose with command
2. Observe container constantly restarting with below error

Environment

- OS: Ubuntu 24.04
- How docker service was installed: docker official

CPU architecture

x86-64

Docker creation

name: downloaders

x-common-labels: &common-labels
  com.centurylinklabs.watchtower.enable: "true"

x-cert-label: &cert-label
  server.custom.cert: "true"

x-common: &common
  labels: *common-labels
  extra_hosts:
    - "host.docker.internal:host-gateway"
    - "${LAXSS_PLEX_DOMAIN}:host-gateway"
  restart: unless-stopped
  networks:
    - downloaders_network

x-common-env: &common-env
  TZ: ${TZ}

x-linuxserver-arr-mods-env: &linuxserver-arr-mods-env
  DOCKER_MODS: linuxserver/mods:universal-package-install
  INSTALL_PACKAGES: openssl

x-media-volume: &media-volume ${LAXSS_MEDIA_PATH}:/media
x-modcache: &modcache ${LAXSS_MODCACHE_PATH}:/modcache

x-ssl-pfx: &ssl-pfx ${LAXSS_PFX_CERT_PATH}:${CONTAINER_PFX_PATH}:ro
x-ssl-cert: &ssl-cert ${LAXSS_SSL_CERT_PATH}:${CONTAINER_SSL_CERT_PATH}:ro
x-ssl-key: &ssl-key ${LAXSS_PRIVATE_KEY_PATH}:${CONTAINER_PRIVATE_KEY_PATH}:ro

services:
  lazylibrarian:
    <<: *common
    image: lscr.io/linuxserver/lazylibrarian:latest
    shm_size: 128M
    container_name: lazylibrarian
    command: "--port ${LAZYLIBRARIAN_PORT}"
    labels:
      <<: [*common-labels, *cert-label]
    healthcheck:
      test: |
        curl -ILkfs --max-time 3 https://localhost:${LAZYLIBRARIAN_PORT}/api > /dev/null \
          && openssl s_client -connect localhost:${LAZYLIBRARIAN_PORT} < /dev/null 2>/dev/null \
            | openssl x509 -noout -checkend 0 > /dev/null 2>&1 \
          || exit 1
      start_period: 120s
      interval: 30s
      timeout: 20s
      retries: 3
    environment:
      PUID: ${LAZYLIBRARIAN_PUID}
      PGID: ${DOWNLOADERS_PGID}
      # DOCKER_MODS: linuxserver/calibre-web:calibre|linuxserver/mods:lazylibrarian-ffmpeg|linuxserver/mods:universal-package-install
      <<: *common-env
    volumes:
      - /volume1/docker/downloaders/lazylibrarian/config:/config
      - *media-volume
      - *modcache
      - *ssl-cert
      - *ssl-key
    ports:
      - ${LAZYLIBRARIAN_PORT}:${LAZYLIBRARIAN_PORT}

networks:
  downloaders_network:
    external: true

Container logs

/run/s6/basedir/scripts/rc.init: 76: --port: not found

[github-actions]

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

[aptalca]

Just change the left side in the port mapping

[Salvora]

The purpose of the command "--port" is to change the container port of lazy librarian web server not the host.

[Roxedus]

setting the cmd (command, in compose) is not supported in most of our images( including this one). the most supported way to achieve your goal is to set the port in the config file in persistent data.

[aptalca]

Rox, they don't even need to change the internal port as they're using a bridge network and port mapping.

Salvora, in your compose, you are doing - ${LAZYLIBRARIAN_PORT}:${LAZYLIBRARIAN_PORT}. Instead, do - ${LAZYLIBRARIAN_PORT}:5299 as that's how docker port mapping works. It's explained in the readme: https://github.com/linuxserver/docker-lazylibrarian?tab=readme-ov-file#parameters

If you really have a valid reason to change the internal port, you have not provided it.

[Salvora]

setting the cmd (command, in compose) is not supported in most of our images( including this one). the most supported way to achieve your goal is to set the port in the config file in persistent data.

I see, is it possible to map these commands to env then? Since they are currently useless.

Rox, they don't even need to change the internal port as they're using a bridge network and port mapping.

Salvora, in your compose, you are doing - ${LAZYLIBRARIAN_PORT}:${LAZYLIBRARIAN_PORT}. Instead, do - ${LAZYLIBRARIAN_PORT}:5299 as that's how docker port mapping works. It's explained in the readme: https://github.com/linuxserver/docker-lazylibrarian?tab=readme-ov-file#parameters

If you really have a valid reason to change the internal port, you have not provided it.

Hey @aptalca I know this is not exactly a big issue and I can manipulate the host port since the container port cannot be changed via compose. The purpose is to produce an easy to read compose file with structured envs.

[aptalca]

No, currently there is no environment var for such command options in this image. If there is a legitimate need for any of the options, we'll consider adding a var. I'm afraid the reason you provided does not meet criteria.