Remove dependency on outdated cross images about akri HOT 6 CLOSED

Hi,
Really interesting subject. I used buildx qui a few times on other projects but never heard of this opensuse service.

Have you also had a look on xx project ? https://github.com/tonistiigi/xx#rust

And do we know what cause armv7 build to fail ? is it rust code ? a dependency ?

from akri.

Hi, Really interesting subject. I used buildx qui a few times on other projects but never heard of this opensuse service.

This openSUSE service is now used by kubernetes to build their artifacts. This is also what is used to build all openSUSE

Have you also had a look on xx project ? https://github.com/tonistiigi/xx#rust

I didn't know about the xx project, will take a look at it

And do we know what cause armv7 build to fail ? is it rust code ? a dependency ?

The armv7 build fails on the opcua crate build, so only the opcua discovery handler fails to build in fact.
It seems to be some kind of error during rust code compilation specific to armv7 flavor of rustc, I didn't file a bug on rustc upstream yet as I didn't take time to try to gather more information about the issue to file a meaningful bug-report for them.

from akri.

About armv7, upstream kubernetes no longer build for armv7 since kubernetes/kubernetes#115742, so I've been wondering if we have any user of that armv7 flavor or if it would be better to just stop providing armv7 builds if these are basically unused.

from akri.

Looking at the downloads from GHCR there are still a few downloads (similar number as arm 64bit so maybe some people download all images ?).

from akri.

I think we should follow suit with Kubernetes and remove v7 support especially if it prevents us from improving our build system.

@diconico07 I am a big fan of reducing container size. Does strategy 1 of using opensuse base and the docker buildx toolkit reduce image size too?

I think the RPM approach is too prohibitive for the local/maintainer experience. It is helpful being able to build images locally and test and run them. But we could potentially do both, publish the RPM containers and still maintain a set of dockerfiles for local builds

from akri.

The way I use to reduce the container size is based on RPM (the image will only have the RPM and its dependencies), so no the pure buildx image is not lighter, it could be made lighter, but this would require more work.

I however agree that not being able to build local images is bad, if we keep all the files simple to maintain (i.e RPM specfile, RPM based Dockerfile and local build Dockerfile) it shouldn't be an issue to have both ways.

For the v7 thing I created rust-lang/rust#115674 for the issue (it won't be hard to bring it back if this get fixed).

from akri.