Unable to find image for version v25.02

[kale1d0code]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

searching for the docker image lscr.io/linuxserver/bookstack:25.02 and getting an error stating the manifest is unknown.

Is this indeed the latest version of the image?

Expected Behavior

to pull new image and start bookstack

Steps To Reproduce

1. create bookstack service stack using any former version.
2. change tag from what it was to "25.02"

Environment

- OS: AlmaLinux 9.2 (Turquoise Kodkod)
- How docker service was installed:
Official Documentation from Docker website (add repo and install from package manager)

CPU architecture

x86-64

Docker creation

volumes:
  <REDACTED>
secrets:
  <REDACTED>
networks:
  public:
    external: true
    name: public
  backend:

services:
  bookstack:
    image: lscr.io/linuxserver/bookstack:${BOOKSTACK_VERSION}
    restart: always
    depends_on:
    - dbms
    volumes:
    - data:/config
    environment:
    - APP_DEBUG=false
    - APP_URL=https://${DOMAIN_NAME}
    - DB_HOST=dbms
    - FILE__DB_DATABASE=/run/secrets/db_name
    - FILE__DB_USER=/run/secrets/db_user
    - FILE__DB_PASS=/run/secrets/db_pass
    - MAIL_DRIVER=smtp
    - MAIL_HOST=<REDACTED>
    - MAIL_PORT=<REDACTED>
    - MAIL_ENCRYPTION=<REDACTED>
    - MAIL_USERNAME=<REDACTED>
    - FILE__MAIL_PASSWORD=/run/secrets/mail_pass
    - MAIL_FROM=<REDACTED>
    - MAIL_FROM_NAME=<REDACTED>
    - AUTH_METHOD=saml2
    - AUTH_AUTO_INITIATE=true
    - SAML2_USER_TO_GROUPS=true
    - SAML2_GROUP_ATTRIBUTE=<REDACTED>
    - SAML2_REMOVE_FROM_GROUPS=true
    - SAML2_NAME=SSO
    - SAML2_EMAIL_ATTRIBUTE=<REDACTED>
    - SAML2_EXTERNAL_ID_ATTRIBUTE=<REDACTED>
    - SAML2_DISPLAY_NAME_ATTRIBUTES=<REDACTED>
    - SAML2_IDP_ENTITYID=<REDACTED>
    - SAML2_IDP_SSO=<REDACTED>
    - SAML2_IDP_SLO=<REDACTED>
    - FILE__SAML2_IDP_x509=/run/secrets/saml_cert
    secrets:
    - saml_cert
    - mail_pass
    - db_pass
    - db_user
    - db_name
    networks:
    - public
    - backend

  dbms:
    image:  mariadb:${DBMS_VERSION}
    restart: always
    command:
    - --skip-log-bin
    healthcheck:
      test:  out=$$(mysqladmin ping -h localhost -P 3306 -u $$(cat $${MARIADB_USER_FILE}) --password=$$(cat $${MARIADB_PASSWORD_FILE}) 2>&1); echo $$out | grep 'mysqld is alive' || { echo $$out; exit 1; }
      start_period: 3s
      interval: 45s
      timeout: 10s
      retries: 3
    environment:
    - MARIADB_ROOT_PASSWORD_FILE=/run/secrets/dbms_root_pass
    - MARIADB_DATABASE_FILE=/run/secrets/db_name
    - MARIADB_USER_FILE=/run/secrets/db_user
    - MARIADB_PASSWORD_FILE=/run/secrets/db_pass
    - MARIADB_AUTO_UPGRADE=
    - TZ=${TIME_ZONE}
    secrets:
    - db_name
    - db_user
    - db_pass
    - dbms_root_pass
    volumes:
    - dbs:/var/lib/mysql
    networks:
    - backend

Container logs

N/A

[ssddanbrown]

@kale1d0code Looks like there is a version-v25.02 tag. Might be better off using that format as it appears fairly consistent looking across images.

[aptalca]

https://www.linuxserver.io/blog/docker-tags-so-many-tags-so-little-time

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

[kale1d0code]

I have solved the issue,
my stack was not including the v at the beginning of the tag
was
25.02
should have been
v25.02