Changelog of the Podman orchestrator

1.4 (2026-10-06)

This version contains breaking changes. Actions to perform during the update are flagged with Migration.

  • Renamed the web service to web-application
    • Migration: in the custom configuration files of the /etc/cyberwatch/configs-enabled directory, rename the web service to web-application. Otherwise, the override is no longer applied and the cyberwatch restart command fails on the web service: the application starts, but no longer restarts automatically with the server
    • Migration: adapt the tools that rely on the container name, which becomes cbwonpremise_web-application_1
    • The cyberwatch logs web and cyberwatch exec web commands are still accepted
  • Added cosign 3 or later to the dependencies of the cyberwatch-podman package, to verify the signature of the images
    • Migration: in offline mode, install the cosign package at the same time as the cyberwatch-podman package
  • The certificate presented by the web interface is now stored in the /etc/cyberwatch/ssl directory instead of the cbwonpremise_data_ssl Podman volume
    • The existing certificate is migrated automatically during the update, and the old volume is kept
  • Added the --force-pull option to the cyberwatch start and cyberwatch restart commands to download the images even if the CBW_NO_PULL variable is enabled in the config.env file
  • The cyberwatch start command now downloads the new images, except with the --no-pull option. This command does not back up the database: prefer cyberwatch restart to update Cyberwatch
  • cyberwatch restart now continues the restart with the images already present on the node when it fails to download the new images
  • Added support for a custom port for the backup and restore of an external database via the MYSQL_PORT variable in the containers.env file
  • The locally modified config.env file is kept during the update of the RPM package. If the package provides a new version of this file, it is saved in config.env.rpmnew
  • Fixed the permissions of the containers.env file on hardened systems configured with a umask of 077, which prevented Cyberwatch from starting. The permissions of an existing file are fixed at the next cyberwatch configure

1.3 (2026-05-05)

  • Added the possibility to scale containers: web, container-scanner and sidekiq_node
  • Added an option to renew expired certificates with cyberwatch renew-certificates
  • Forced the usage of the root-ca during database backups
  • Fixed the generation of the Cyberwatch root-ca

1.2 (2025-11-21)

  • The cyberwatch logs command allows viewing logs of stopped containers
  • Fixed the paths for certificates used by Redis
  • Fixed a problem that prevented the application from restarting when using the button
  • Fixed a problem on Ubuntu systems that prevented some containers from restarting after the machine rebooted

1.1 (2025-10-29)

  • Fix for the web-scanner container allowing nmap scans to be launched

1.0 (2025-10-21)

  • First version of the Podman orchestrator