-
Notifications
You must be signed in to change notification settings - Fork 340
Kernel Devel error when building Cortx in docker #864
Comments
@shailesh-vaidya, please address the issue as reported? |
@harrison-seow-seagate Thanks for trying out Docker image. To debug issue can you please post the output of following commands from the system on which you are executing
|
Hi @shailesh-vaidya, please refer the output below, thanks.
|
@harrison-seow-seagate Thanks for the command output's. Seems you are trying to generate Build on You can use image TAG to identify OS Version for it. e.g. Please try Build process on |
I see, thanks @shailesh-vaidya, I will try it out again in a newer version. |
This issue/pull request has been marked as |
@harrison-seow-seagate Please let us know if you are able to build CORTX packages on CentOS 7.8.2003 system. Let me know if any help needed. |
Hi @shailesh-vaidya, I have a rather slow Internet speed, so it will take me some time to download the new OS and rebuild Cortx. |
Hi @shailesh-vaidya , I have just tested it out today and although the output is different but I'm still seeing a very similar RPM build error. Output Snippet
Machine Info
Script to Reproduce
|
Hi @harrison-seow-seagate - Hare Build was failing due to a new dependency added. It's fixed now. Please pull the latest image and try to build again.
|
Thanks @shailesh-vaidya, I pulled the latest image and it worked. I'll close this issue as it's resolved. |
Attempt 1
Following this guide, I wanted to build Cortx using the cortx-build image. However, I encounter the following error:
Attempt 2
So I thought perhaps it's missing the kernel devel, and I opened an interactive shell
docker run --rm -v /var/artifacts:/var/artifacts -v /root/cortx:/cortx-workspace -it ghcr.io/seagate/cortx-build:centos-7.8.2003
Manually install a kernel devel before building
It went past the initial stage, but then failed again (error_output.txt) at a later stage
Script to reproduce
Using VMWare Workstation 16 Player (Windows 10) running CentOS 7.7.1908
The text was updated successfully, but these errors were encountered: