Open arcivanov opened 9 months ago
Managed to switch to make sysbox-local
with Requires: libseccomp
and BuidRequires: libseccomp-devel
. The sysbox-static-local
stopped building on CentOS/RHEL due to there not being static versions, i.e. libseccomp-static
.
Hi @arcivanov, apologies for breaking that; I develop Sysbox on a Ubuntu host, so did not see the problem you report.
Do I need to depend on the system's libseccomp[-devel] now?
I am not sure, but probably yes, because you need the C libraries for libseccomp, so libseccomp-golang can reference them.
In general the switch I did is beneficial, because it makes Sysbox use upstream libseccomp & libseccomp-golang, rather than a forked version that we created a couple of years ago as libseccomp did not yet implement the functionality we needed.
If you have any further info on how to overcome the problem, please share it. Even better, if you can add the fixes on the appropriate Dockerfile here, that would be great.
Thanks!
Will do.
Hey @arcivanov did you find a workaround? I have the same issue on AL2 using make sysbox-static
although I see libseccomp-devel
included in the Dockerfile here.
I get during the go build:
# github.com/nestybox/sysbox-runc
/usr/local/go/pkg/tool/linux_amd64/link: running gcc failed: exit status 1
/usr/bin/ld: cannot find -lseccomp
/usr/bin/ld: cannot find -lseccomp
collect2: error: ld returned 1 exit status
Full logs are available here: https://download.copr.fedorainfracloud.org/results/karellen/karellen-sysbox/fedora-38-x86_64/06680595-karellen-sysbox/builder-live.log.gz
Do I need to depend on the system's
libseccomp[-devel]
now?