vendor: drop override for github.com/opencontainers/runc#19817
vendor: drop override for github.com/opencontainers/runc#19817giuseppe wants to merge 1 commit intocontainers:mainfrom
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: giuseppe The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ede4dc1 to
6af4701
Compare
|
shurg, we are pulling in a huge new dependency (github.com/cilium/ebpf). As usual, I forgot to run |
|
I think there's still some vendor-dependency fart. The main branch of runc doesn't require cilium anymore. But trying to vendor that will revert many other dependencies. |
|
I still see cilium in the latest revision: https://github.com/opencontainers/runc/blob/main/go.mod#L7 and I get the same bloat locally: it is 59137488 vs 58094336 @kolyshkin do you think it would make sense to have a build tag to drop ebpf? |
|
I noticed that common is also replacing runc. I guess we need to start there. |
6af4701 to
2045060
Compare
|
opened a PR for runc to allow disabling eBPF support: opencontainers/runc#4005 let's see if that breaks any test |
da90610 to
1009bb2
Compare
|
@kolyshkin I am using the latest HEAD version here, still the binary size grew by 836320 bytes that is why the package is referenced by: |
aade16b to
bf8fc65
Compare
|
temporary version bump until there is a new runc version: #19854 |
|
A friendly reminder that this PR had no activity for 30 days. |
Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com>
bf8fc65 to
7562606
Compare
|
rebased and testing: containers/common#1633 |
|
The system failures look consistent |
|
runc is still bloated, the last version didn't fix the dependency issue with EPBF (reported here: opencontainers/runc#4005), I'll close this PR for now |
podman builds fine with the latest runc, so we can drop the override.
Closes: #19795
Does this PR introduce a user-facing change?