Stucked when following "Wazuh packages generation guide"

[Klein Mee]

I was using local source code to build rpm packages in centOs7. Docker is well prepared, but everytime I try to build with "./generate_debian_package.sh -b v4.4.5 --packages-branch v4.4.5 -t agent -a amd64 -p /opt/ossec --sources /root/wazuh-master/src/" , the process will stuck at "RUN curl -OL http:......"

What does "Shared 36..." mean? Can you give me some suggestions to solve it? Thanks.

[Stuti Gupta]

Thanks for using Wazuh!

I am looking into this request, I will get back to you with the proper approach to achieve this.

Regard,
Stuti

[Stuti Gupta]

Hi team,

Hope you are doing well

We tested the Wazuh Docker deployment using methods that are mentioned in wazuh documentation https://documentation.wazuh.com/current/deployment-options/docker/wazuh-container.html  and this documentation working fine in our lab.

Can you please share the following information, so we can provide you with an accurate solution to your query:

• Can you please let us know the steps that you are following?
• Please share the  OS details using this command: cat /etc/os-release

Hope to hear from you soon.

Regard,
Stuti

[Klein Mee]

Thanks，

First, steps I followed:

(1)download wazuh-master and wazuh-packages-master, unzip them

(2)configure docker with doc:https://docs.docker.com/engine/install/centos/, and test it by "docker run hello-world" 

(3)then followed "Wazuh packages generation guide/RPM":

https://documentation.wazuh.com/current/development/packaging/generate-rpm-package.html

finally excute "./generate_rpm_package.sh -b v4.4.5 --packages-branch v4.4.5 -t agent -a x86_64 -p /opt/ossec --sources /root/wazuh-master/src/"

(4)result: the process stop at: "[14/17] RUN....", it takes about 20mins to get there.

 

About other configurations: The CentOs7 VM has 8 GB of memory and 40 GB of disk space. Also, I live in China and use clash for windows to speed up pull, and add /etc/docker/daemon.json for docker until docker run hello-world excute successfully. Physical machines and virtual machines are connected in bridge mode and share the VPN. And I have tried generate debs on ubuntu22.04, the result looks like the same.

result on ubuntu22.04:

Second:

If the problem is because of my network configuration?

[Stuti Gupta]

Hi againCan you please tell us the version of docker-compose you are using? It is recommended to use Docker Compose version v2.12.2. To check the docker version you can use the following command.
docker-compose --version
To install that version you can refer to this document. https://documentation.wazuh.com/current/deployment-options/docker/docker-installation.html.
Once you install this Docker Compose version v2.12.2. You can follow this document of building RPM packages.
https://documentation.wazuh.com/current/development/packaging/generate-rpm-package.htmlHope this will help you out. Please feel free to reach out to us for any information/issue.

Regars,
Stuti Gupta

[Klein Mee]

Hi，

First, I notice the "docker" I deployed is actually "docker engine", so I made a mistake. Then, I deployed docker refering to the document you mentioned. But the command "./generate_rpm_package.sh -b v4.4.5 --packages-branch v4.4.5 -t agent -a x86_64 -p /opt/ossec --sources /root/wazuh-master/src" makes the process not ending.

Anything wrong with the absolute path "/root/wazuh-master/src"? It means the path where I downloaded wazuh-master.zip and unzip it,

[Klein Mee]

Hi， 

Considering about time consuming of "make install" is probably much longer than I thought,  I decide to be more patient about this process.

Again, thanks for your help!

[Klein Mee]

Hi,

It shows that the process took about 70mins to finish, but there is still a error:

[Klein Mee]

Hi,

I added an option --dev to avoid this step "+ curl -L https://raw.githubusercontent.com/wazuh/wazuh-packages/v4.4.5/rpms/SPECS/wazuh-agent.spec -o /downloaded_tmp_specs/wazuh-agent.spec", finally made it.

[Stuti Gupta]

Hi team,
Sorry for late responseGlad to know that its working and thank you for notifying us.
Please do not hesitate to contact us for any information/issues.

Regards,
Stuti Gupta