What's new

batect now supports connecting to the Docker daemon over TCP.
batect now supports configuring the target Docker daemon, either through the DOCKER_HOST environment variable or with the --docker-host command line option.
The formatting of the summary shown after a task finishes has been improved, and longer durations will now be shown in a more understandable format. For example, instead of "600.0 seconds", you'll see "10m 0s".
It is now possible to override the working directory for a task's main container. For example, in the following example, the build-env container will be started in the /task-override directory when the build task is run:
```
containers:
  build-env:
    working_directory: /container-default

tasks:
  build:
    run:
      container: build-env
      working_directory: /task-override
```
The comparison with other tools in the documentation has been expanded to discuss using CI tools' local runners in comparison with batect.

Getting started

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

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