github batect/batect 0.60.0

latest releases: 0.85.0, 0.84.0, 0.83.9...
3 years ago

Changes in this release:

  • New: batect now includes experimental support for building images with BuildKit.

    BuildKit significantly improves the performance of image builds, particularly multi-stage builds, and introduces some new features. (batect does not yet support all of these new features, such as securely using secrets in image builds.)

    Enable BuildKit by passing the --enable-buildkit flag or setting the DOCKER_BUILDKIT environment variable to 1.

    BuildKit support is considered experimental. If you encounter any issues, please file an issue.

    There is one known issue: the Dockerfile is incorrectly included in the build context when building an image with BuildKit. This is only problematic if your Dockerfile includes a COPY instruction that copies the entire build directory into the image. This issue will be fixed in a future release.

  • New: configuration error messages now include more detailed information.

    Configuration error messages now include YAML path information, in addition to line and column references (eg. error at containers.build-env.blah on line 16, column 10: ...). This also makes it easier to understand errors introduced through merging or aliases.

  • Improved: the performance of waiting for a container to become healthy has been improved.

  • Improved: the Golang page in the documentation now includes advice on how to configure caching for golangci-lint, significantly improving its performance.

  • Changed: further information will now be reported in telemetry, as mentioned on the privacy page of the documentation: image build times, Linux distribution name (eg. Ubuntu or CentOS) and the image builder used (legacy builder or BuildKit)

  • Fixed: the wrapper script will no longer produce any output when the BATECT_QUIET_DOWNLOAD environment variable is set (thanks to @hpcsc for reporting this issue in #549)

Getting started

First time using batect? Take a look at the getting started guide, or the many sample projects.

How to upgrade from previous versions

If you're already using batect, run ./batect --upgrade to upgrade automatically.

Don't miss a new batect release

NewReleases is sending notifications on new releases.