diff --git a/themes/default/content/blog/build-images-50x-faster-docker-v4/index.md b/themes/default/content/blog/build-images-50x-faster-docker-v4/index.md index 5a3c066e065..58d767daceb 100644 --- a/themes/default/content/blog/build-images-50x-faster-docker-v4/index.md +++ b/themes/default/content/blog/build-images-50x-faster-docker-v4/index.md @@ -38,7 +38,7 @@ tags: The [Pulumi Docker Provider](/registry/packages/docker) has been a top Pulumi provider since it launched in 2018. It can be used to provision any of the resources available in Docker, including containers, images, networks, volumes and more. -One of the most heavily used features of this provider is the `docker.Image` resource, which enables Pulumi users to build and (optionally) push a local Docker context (like an application folder) to a registry as part of a Pulumi deployment. Today we are excited to announce a set of improvements to the `docker.Image` Resource driven by the feedback we have received from our community. This set of improvements includes: +One of the most heavily used features of this provider is the `docker.Image` resource, which enables Pulumi users to build and (optionally) push a local Docker context (like an application folder) to a registry as part of a Pulumi deployment. Today we are excited to announce a set of improvements to the `docker.Image` resource driven by the feedback we have received from our community. This set of improvements includes: * Significantly improved performance (including reduced need for rebuilds) * BuildKit support (including cross-platform builds) @@ -47,11 +47,11 @@ One of the most heavily used features of this provider is the `docker.Image` res -### Significantly improved performance +Our friends Nikhil Benesch and the Materialize team created a Docker image provider that demonstrated better workflows with Docker BuildKit and we’re excited to finally make these improvements part of our official Pulumi Docker Provider. -To improve the efficiency of the Docker Provider, we have changed the default behavior to rebuild only on context change. In addition, the `cacheFrom` option now offers the ability to use a registry as the image cache. By leveraging BuildKit and caching improvements, subsequent rebuilds may be up to 50x faster. This functionality and other improvements of the Docker Provider we are announcing today are [highly requested from our community](https://github.com/pulumi/pulumi-docker/issues/132). +### Significantly improved performance - +To improve the efficiency of the Pulumi Docker Provider, we have changed the default behavior to rebuild only on context change. In addition, the `cacheFrom` option now offers the ability to use a registry as the image cache. By leveraging BuildKit and caching improvements, subsequent rebuilds may be up to 50x faster. This functionality and other improvements of the Pulumi Docker Provider we are announcing today are [highly requested from our community](https://github.com/pulumi/pulumi-docker/issues/132). ### BuildKit support @@ -76,25 +76,25 @@ const img = new docker.Image("my-image", { }); ``` -## Rich Docker build logs inside Pulumi IaC program output +### Rich Docker build logs inside Pulumi IaC program output Filtered docker logs during build and push will now be displayed in the Info box on pulumi up. [![asciicast](https://asciinema.org/a/I8Xzmfme56ZP4uD6uo2U4i2wr.svg)](https://asciinema.org/a/I8Xzmfme56ZP4uD6uo2U4i2wr) ### Pulumi YAML and Pulumi Java support -We announced [Pulumi YAML and Pulumi Java](https://www.pulumi.com/blog/pulumi-universal-iac/) last year and are excited to have extended support to the Pulumi Docker Provider. This release schematizes all Docker resources, which enables auto-support of all Pulumi languages. In addition, this means the Docker image resource can now participate in the CRUD (create, replace, update, delete) lifecycle. +We announced [Pulumi YAML and Pulumi Java](https://www.pulumi.com/blog/pulumi-universal-iac/) last year and are excited to have extended support to the Pulumi Docker Provider. This release schematizes all Docker resources, which enables auto-support of all Pulumi languages. In addition, this means the `docker.Image` resource can now participate in the CRUD (create, replace, update, delete) lifecycle. ### Migrating to 4.0 -The 4.0 version of the Docker provider consists of a significant overhaul of the Image Resource. -As a result there are some breaking changes to the behavior of the Image resource and supporting types, as well as some minor name changes. +The 4.0 version of the Pulumi Docker Provider consists of a significant overhaul of the `docker.Image` resource. As a result there are some breaking changes to the behavior of the `docker.Image` resource and supporting types, as well as some minor name changes. + +As the `docker.Image` resource does not manage any backend state, updating to the 4.0 version does not require any resource imports or stack updates. -Happily, since the Image resource does not manage any backend state, migrating to this version does not need any resource imports or stack updates. -For most use cases, migrating should be as straightforward as updating your `pulumi-docker` version to 4.0.0 and adjusting your code to reflect the updated types. +For most use cases, migrating should be as simple as updating the `pulumi-docker` version to 4.0.0 and adjusting the Pulumi program code to reflect updated types. -Please find the detailed migration guide, in the [release notes for v4.0.0](https://github.com/pulumi/pulumi-docker/releases/tag/v4.0.0). +Please find the detailed migration guide in the [release notes for v4.0.0](https://github.com/pulumi/pulumi-docker/releases/tag/v4.0.0). ### Getting started -The Docker Provider Image Resource has everything you need to build, run, and push Docker images for any container registry. Visit [Docker installation and configuration](https://www.pulumi.com/registry/packages/docker/installation-configuration/) page to start building your next image now! +The Pulumi Docker Provider has everything you need to build, run, and push Docker images for any container registry. Visit the [Docker installation and configuration](https://www.pulumi.com/registry/packages/docker/installation-configuration/) page to start building your next image now!