Use specific tag for BuildKit

[SaschaSchwarze0]

Changes

In our sample build strategies for BuildKit, we never used a specific version as tag. Instead, we used nightly which is the main branch. This finally broke us as our e2e are failing:

  #9 ERROR: process "/bin/sh -c pwd &&     ls -l &&     npm install &&     npm run print-http-server-version" did not complete successfully: buildkit-runc did not terminate successfully: exit status 1: unable to destroy container: unable to remove container's cgroup: open /sys/fs/cgroup/5aqt7rzovvis0vrkm6iuwynpu: no such file or directory

I am hereby changing the strategy to use the images of the latest BuildKit release instead. This is inline with everything comparable that we have (kaniko, buildah).

A separate PR will be needed to add automatic bumping of the image tag on a new version.

Submitter Checklist

• Includes tests if functionality changed/was added
• Includes docs if changes are user-facing
• Set a kind label on this PR
• Release notes block has been filled in, or marked NONE

Release Notes

The sample build strategy for BuildKit now uses the latest BuildKit release instead of its nightly build

[qu1queee]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qu1queee

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [qu1queee]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment