provide build using Containerfiles

[benoitf]

Is your feature related to a problem? Please describe

Today, the build is done purely inside GitHub runners (having the Node.js dependency, package manager, etc)

Some other projects are providing Containerfile (one for the builder and one for the extension) allowing to quickly build the extension without any dependency installed on the system (except the OCI runtime like podman, docker, etc)

example:
https://github.com/podman-desktop/extension-kubernetes-dashboard/tree/main/build
https://github.com/podman-desktop/extension-apple-container/tree/main/build

(and see usage inside .github/workflows)

Describe the solution you'd like

Introduce a build directory with Containerfile to have a build being possible without requiring GitHub runner / workflow so we really know what is provided to the building tools steps.

Describe alternatives you've considered

keep it like it is

Additional context

[axel7083]

Following the standup, I am not sure to understand why we have two containerfile? Why not using multi stage containerfile? One with target builder, and one for the final output ?

[benoitf]

caching performance

[benoitf]

or call it distributed-cache performance.

[benoitf]

when using docker buildx there is the --cache-from etc but there is no equivalent on podman, this is why people introduced a dedicated builder image to do caching(builder image is updated only if dependencies are updated)