Added a check during container startup to prevent the deletion of images for containers that have not yet been started
Fixed the display of a warning related to the use of the CBW_DONT_PRUNE_UNUSED_IMAGES option
New images are now pulled before stopping the stack to minimize application downtime
5.26 (2025-03-18)
Fixed a volume issue when configuring a node as an offline satellite
Removed support for MicroK8s orchestrator
The IP address of the Docker network used for container-scanner has been configured to be in a similar range to the default Docker network
5.25 (2025-01-06)
Automatically sets privileged: true for the container-scanner service, if the kernel version of the machine hosting Cyberwatch is lower than 5.11
The configuration file /etc/cyberwatch/configs-enabled/compose-service/container-scanner.yml has been renamed to /etc/cyberwatch/configs-enabled/compose-service/35-container-scanner.yml for the container-scanner service.
Fixed a problem in the order of use of configuration files in /etc/cyberwatch/configs-enabled/
5.24 (2024-12-10)
Improved cyberwatch commands for container-scanner:
Add cyberwatch exec container-scanner command
Add cyberwatch log container-scanner command
Add container-scanner when executing cyberwatch status
Improved timeout when using the cyberwatch restart command
Fixed a problem when importing the security database for offline instances. The new command is cyberwatch exec sidekiq_master security_database_import_task
Moved the directory where the container-scanner service is stored to /etc/cyberwatch/configs-enabled/compose-service/container-scanner.yml
Private keys created with cyberwatch configure now have a size of 3072 bits
5.23 (2024-10-28)
Fix an update error with the config.env file when installing the deb package
Fix an error that could occur in the post-installation script with an old version of bash
5.22 (2024-10-16)
Fix failure to update container-scanner image
5.21 (2024-10-07)
Remove the migration from cbw-on-premise v2.X to cbw-on-premise 5.X
The new procedure involves reinstalling Cyberwatch. Do not hesitate to contact support for more information
The web, sidekiq, sidekiq_master and sidekiq_node containers are now run with a non-privileged user
Remove the cron service
Added a sidekiq_master service available only on the master node