Migrate from Kaniko to BuildKit

[fahedouch]

Hi dib Folks,

I propose switching dib build process from Kaniko to BuildKit. This change is motivated by the fact that Kaniko is no longer maintained, and BuildKit offers a more feature-rich and integrated solution.

Reasons for Migration

• Kaniko is No Longer Maintained:
  Kaniko is no longer actively maintained, posing a risk for future security vulnerabilities.

  • State of Kaniko: Unmaintained? GoogleContainerTools/kaniko#3348
  • chore: remove @zhangquan and @jeromeju from maintainer list GoogleContainerTools/kaniko#3345
  • [Sandbox] Kaniko cncf/sandbox#88 (comment) [CNCF sandbox refused]

• BuildKit Offers More Features:
  Supports multi-architecture builds and other advanced features not available in Kaniko.

• Better Ecosystem Integration:
  BuildKit is the default build worker for containerd, which is widely used in managed Kubernetes services (GKE, EKS, AKS).

• Extensive Feature Set:
  BuildKit has many features not present in Kaniko. Visit the BuildKit repository for more details.

• Expertise and Community Support:
  As a maintainer of nerdctl in the containerd community, I have more experience and contacts within the BuildKit ecosystem. Who knows, it might help move things forward. ¯_(ツ)_/¯

• Roadmap assurance:
  roadmap features seems to be easily addressed with buildkit than kaniko.

as we are planning to release the v1.0 soon, I prefer release the v1.0 with buildkit

related issue ticket:

• Setting up script and documentation to configure buildkit #697

Since it's my first post at DIB, I wanted to add a bit of warmth with this beautiful landscape 😍