Victor Ereñú

## Centos 7 without :z option ``` console [root@ip-172-31-45-119 single-node]# sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: enforcing Mode from...

## Centos 7 with :z option ``` console [root@ip-172-31-45-119 single-node]# sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: enforcing Mode from...

Hello @levisre I have carried out tests on several computers and I have not been able to reproduce the error that you mentioned regarding this topic in the issue https://github.com/wazuh/wazuh-docker/issues/711....

Hi @gajetto We are working in a new major version of Wazuh and we included jammy support in the new release so it is not necessary to add this PR,...

The manifest was updated for the installation of Wazuh with Puppet according to the changes reflected in the Wazuh documentation: ``` ruby $discovery_type = 'single-node' stage { 'certificates': } stage...

The method for creating the Wazuh stack deployment manifest was modified. I performed a test operation of the command in bash: ``` console root@ip-172-31-34-117:~# hostname=Prueba root@ip-172-31-34-117:~# sudo cat Stage[repo] ->...

Hello @alphaDev23 Have you tried to start the stack with `docker-compose` before generating the stack certificates? In the `docker-compose.yam`l file are all the certificates mounted in their respective locations, so...

The error was caused by the number of alerts that the Wazuh agent takes in the Amazon Linux 2023 environment. This was solved by modifying the number of events that...

I have been carrying out quite a few tests on the PR test and the multi-node deployment test has problems, the runner that executes the test suffers random crashes. I...

The deployment tests were carried out, modifying the code to give more startup time to the stack services and the tests continued to fail:   It was reviewed that...