Introducing Runtime v3 – Multi-arch images and more control over Docker

[#1]

Hi all - we're excited to announce a major enhancement to the Pipelines cloud runtime which is designed to significantly increase customer capabilities when working with Docker.

This new functionality is being made available via a new (totally opt-in) runtime version, configured at the step level in your Pipelines .yaml

The new capabilities enable a whole heap of things, the biggest of which is the use of `docker buildx` and the associated benefits that come with that like multi-arch image builds.

For all the details, check out the launch blog.

[Vilhelm Tamm]

Thank you for finally bringing buildx (almost) to Pipelines Cloud. I read the documentation and found the following part:

Bitbucket Pipelines supports the following caching types:

Remote S3 Cache

[...]

Local

[...]

Seeing as there is no mention of using an external registries (like ECR), I assume setting `type=registry` for buildx caching like in the following example is not yet supported?

- docker buildx create --use
- docker buildx build \
  --tag $IMAGE_URL:$BITBUCKET_BUILD_NUMBER \
  --cache-from type=registry,ref=$IMAGE_URL:buildcache \
  --cache-to type=registry,ref=$IMAGE_URL:buildcache,mode=max \
  --push \
  -f Dockerfile

If true, can you provide any estimate when `type=registry` will be available for us to use in the new runtime?