Tracking Solver Migration

[jonjohnsonjr]

Related: chainguard-dev/go-apk#159

I'm using images as test inputs for any changes I make to the solver. In the fullness of time, we want apko to have parity with apko, but we can't just change the solver algorithm because it would break things in images.

Why would that break things in images? Because we currently have some impossible to solve images that only work because apko is a little bit broken :)

Going to use this issue to track issues I come across and progress towards parity.

Overview

• cni-plugins

cni-plugins

We have a conflict in https://github.com/chainguard-images/images/blob/e88951f95c31d2f1d238ebcc0ff251f30c4e1c29/images/cilium/configs/agent/main.tf

$ apk add cni-plugins-main cilium
WARNING: opening ./../../packages: No such file or directory
fetch https://packages.wolfi.dev/os/aarch64/APKINDEX.tar.gz
ERROR: unable to select packages:
  cni-plugins-1.4.0-r1:
    conflicts: iproute2-6.6.0-r0[cmd:bridge=1.4.0-r1] cni-plugins-main-1.4.0-r1[cmd:bridge=1.4.0-r1] cni-plugins-main-1.4.0-r1[cmd:dummy=1.4.0-r1] cni-plugins-main-1.4.0-r1[cmd:host-device=1.4.0-r1] cni-plugins-main-1.4.0-r1[cmd:ipvlan=1.4.0-r1] cni-plugins-main-1.4.0-r1[cmd:loopback=1.4.0-r1] cni-plugins-main-1.4.0-r1[cmd:macvlan=1.4.0-r1]
               cni-plugins-main-1.4.0-r1[cmd:ptp=1.4.0-r1] cni-plugins-main-1.4.0-r1[cmd:vlan=1.4.0-r1]
    satisfies: cilium-1.14.5-r0[cni-plugins]
  iproute2-6.6.0-r0:
    conflicts: cni-plugins-1.4.0-r1[cmd:bridge=6.6.0-r0] cni-plugins-main-1.4.0-r1[cmd:bridge=6.6.0-r0]
    satisfies: cilium-1.14.5-r0[iproute2]
  cni-plugins-main-1.4.0-r1:
    conflicts: iproute2-6.6.0-r0[cmd:bridge=1.4.0-r1] cni-plugins-1.4.0-r1[cmd:bridge=1.4.0-r1] cni-plugins-1.4.0-r1[cmd:dummy=1.4.0-r1] cni-plugins-1.4.0-r1[cmd:host-device=1.4.0-r1] cni-plugins-1.4.0-r1[cmd:ipvlan=1.4.0-r1] cni-plugins-1.4.0-r1[cmd:loopback=1.4.0-r1] cni-plugins-1.4.0-r1[cmd:macvlan=1.4.0-r1] cni-plugins-1.4.0-r1[cmd:ptp=1.4.0-r1]
               cni-plugins-1.4.0-r1[cmd:vlan=1.4.0-r1]
    satisfies: world[cni-plugins-main]

Because that image depends on:

[
  "bash",
  "busybox",
  "cilium",
  "cilium-container-init-compat",
  "cilium-envoy",
  "cni-plugins-main",
  "gops",
  "mount",
  "util-linux-misc",
  "wolfi-baselayout"
]

And because cilium depends on cni-plugins which provides cmd:vlan=1.4.0-r1, but cni-plugins-main also provides cmd:vlan=1.4.0-r1.

[imjasonh]

Should we have one (or both?) of those packages do a no-provides so Melange SCA doesn't try to detect and report that cmd?

Do they both provide the same cmd=vlan=1.4.0-r1? Or somehow, different ones?

[jonjohnsonjr]

I'm not actually sure what cilium really depends on here... maybe we should just drop the cni-plugins-main in the image config since it's a subset of cni-plugins?

I wonder how hard it is to determine which binaries we actually need...