What's new

The way in which batect schedules and executes the various operations involved in running a task (eg. pulling an image, building an image, creating a container, starting a container etc.) has been nearly completely rewritten to be simpler and more reliable. This means:
- the reliability of cleaning up after a task is significantly improved
- batect can now show more detailed information when something goes wrong, especially during the clean up process, and can show detailed instructions on how to clean up manually in the unusual event this does happen
- making future improvements to batect will be easier, quicker and less error-prone

What's been fixed

If a container's image creates any volumes, these will now be cleaned up correctly and not left dangling.
If any proxy-related environment variables are set on the host, and propagating proxy environment variables is not disabled with --no-proxy-vars, then the names of all containers in the task will be added to the no_proxy and NO_PROXY environment variables. (If either of them are not set, then they will be created and set to the list of all containers in the task.)
This ensures that all inter-container communication is not proxied.
Thanks to @squirmy for finding and reporting this issue offline.

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

If you're using batect 0.12 or newer, run ./batect --upgrade to upgrade automatically.
If you're using an older version of batect, replace the batect script in your project with the one attached to this release. (Don't forget to make it executable with chmod +x batect if need be.)