v0.18 Changes

• If you didn't see the release notes from v0.17.1, know that CPU usage is now well under control. If you ever experience high CPU while using lazydocker, please raise an issue.
• When docker is not running, we now wait for it to start up instead of crashing
• fixed issue where container CPU was reported lower than expected (sometimes at zero percent)
• Less reliance on docker binary (though we're not quite ready to do away with the binary entirely). This makes for noticeably faster loading of container logs
• Updated rendering libary (gocui) includes various bug fixes, supports more terminals (e.g. alacritty), and notably introduces scrollbars! (that you cannot interact with that but are nice regardless)
• We are now sorting images by name for easier browsing
• You can now force remove images (with an admittedly clunky UI for now)
• You can now start (as opposed to restart) a service with shift+S
• Fixed bug where toggling the hiding of stopped containers did not immediately apply
• version info is now built in upon doing go install meaning fewer users should encountered the 'unversioned' version at the bottom left of the screen (instead they'll see the git commit hash)
• Fixed the Dockerfile to support go 1.18
• Performance improvements

Changed defaults

We now wrap content in the main panel by default. You can restore the old behaviour with:

gui:
  wrapMainPanel: false

Timestamps in container logs are no longer shown by default. You can restore them with:

logs:
  timestamps: false

Now that we're using the docker SDK (rather than binary) for viewing container logs, the commandTemplates.containerLogs is now longer recognised. Instead you can configure logging like so:

logs:
  timestamps: false
  since: '60m'

A notable exception to this is that if you press 'm' to view logs on a container we'll still use the binary. That'll also be switched to using the SDK (meaning the above config options will apply to that too) in a future relase.

Note from maintainer

I've closed off quite a few issues as having been resolved, and the issues that remain are surprisingly do-able. Many wanted features like searching in the main panel and resizing panels are already solved problems in lazygit and can be easily ported over.

So, if you're looking for some open source work, or just want to see your desired feature in lazydocker, consider picking up an issue. I'll be happy to give pointers.

As always, thanks to the contributors who help out in the repo and thanks to all my sponsors. If you'd like to support lazydocker's development, please consider sponsoring me by clicking the sponsor button at the top of this page. Every bit helps!