All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Docuum supports a new platform: AArch64 GNU Linux.
- Docuum supports a new platform: macOS on Apple silicon.
- Added
--deletion-chunk-size, thanks to Kulek Alexandr.
- Fixed an issue introduced in v0.21.0 which prevented Docuum from working on Windows.
- On Linux, Docuum now supports percentage-based thresholds such as
--threshold '50%'in addition to absolute thresholds like--threshold '10 GB'.
- Docuum now works with images produced by
kaniko --reproducible, which produces images with timestamps earlier than the UNIX epoch.
- Log levels have been adjusted to give more control over the verbosity of log messages. All
debugmessages were moved totrace, someinfomessages were moved todebug, and the default log level has been changed todebug. This means that the same messages should be logged as before, unless a custom log level has been specified.
- When Docker is not running, Docuum now restarts every 5 seconds instead of every second.
- Docuum now uses a smarter strategy for populating "last used" timestamps for unrecognized images, thanks to a suggestion by Mac Chaffee. Previously, Docuum would default to the image build timestamp when no last used timestamp for that image is known. However, that strategy can occasionally lead to situations in which Docuum would delete an image that was built a long time ago but only recently pulled locally, because Docuum could discover and delete the image before consuming the image pull event. Now, Docuum only defaults to the image build time the first time it runs on a machine, and thereafter it defaults to the current time.
- Docuum now uses a more robust way to determine the images that are currently in use by containers.
- Added the
--keepflag to prevent Docuum from deleting certain images.
- Added a workaround for a bug in the
mcr.microsoft.com/windows/nanoserverDocker image so that Docuum can run in that environment.
- Fixed an incorrect error message.
- The Windows binary is now statically linked, which makes it portable enough to run with the
mcr.microsoft.com/windows/nanoserverDocker image.
- Fixed an issue with the Docker image which was caused by incorrect file permissions.
- Docuum now supports Windows.
- Docuum's dependencies have been updated to their latest versions. There should be no changes in behavior.
- This version is the same as 0.16.0, except for Linux we now distribute musl binaries in addition to the glibc binaries. The
stephanmisc/docuumDocker image is also much smaller now thanks to switching to Alpine Linux (with the new musl release) over Debian Slim.
- Docuum now considers an image to be used when a container is created from it, rather than just when a container is destroyed.
- Fixed a bug which would cause Docuum to crash if the system temporary directory (e.g.,
/tmpis in a different filesystem than the user's local data directory. Thanks Mac Chaffee for the fix!
- Docuum now persists its state atomically. This is to avoid the possibility of having the state only partially written due to abnormal termination, such as from a power failure.
- Docuum now uses the Docker CLI rather than the Docker API to communicate with the Docker daemon. This was motivated by a recent issue in which Docuum mysteriously stopped being able to stream events from Docker. At the time of this writing, it's not clear whether the issue is with Bollard (our Docker API library) or with the Docker API itself, but we know that the Docker CLI continues to work. See fussybeaver/bollard#113 for details. Unfortunately, this is a breaking change because the schema for the state has changed.
- Docuum now persists its state after the initial run on startup, and not just on subsequent runs triggered by Docker events. The bug was introduced in the previous version, v0.13.0.
- Thanks to Matthew Donoughe, Docuum now uses a better algorithm for determining the order in which to delete images. This should make Docuum more efficient and less noisy.
- Docuum now uses the Docker API to communicate with the Docker daemon directly and no longer depends on the Docker CLI.
- When Docuum discovers an image it hasn't seen before, it now bootstraps the "last used" timestamp from the image creation timestamp rather than the current timestamp.
- Reverted the change from v0.10.0 due to a bug in a dependency (see #78).
- Docuum now uses the Docker API to communicate with the Docker daemon directly and no longer depends on the Docker CLI.
- Fixed a bug which caused zombie
docker events ...processes to accumulate over time.
- Docuum no longer considers the
deleteoruntagimage events to be "uses" of the image.
- Fixed a bug in which Docuum would not consider certain image events as "uses" of the image.
- Fixed a bug in which Docuum could enter a crash loop by repeatedly trying to query the ID of an image that no longer exists. This would happen when there is a container that points to such an image.
- In logs, timestamps are now displayed in the local time zone (along with the UTC offset).
- Unrecognized images are considered to be brand new, rather than as old as the UNIX epoch.
- Docuum now listens for the
container destroyevent rather than thecontainer dieevent.
- Docuum now wakes up when an image is imported or loaded, not just when an image is built or pulled.
- Docuum now wakes up when an image is pulled, not just when an image is built.
- Fixed some incorrect error messages and log lines.
- Optimized the number of disk writes.
- Added timestamps to the log format.
- Renamed the
-c("capacity") option to-t("threshold") as a follow-up from the change introduced in v0.3.0. - Docuum now automatically restarts itself when an error occurs.
- Docuum now cleans up the
docker eventschild process when an error occurs.
- Renamed the
--capacityoption to--threshold.
- Initial release.