Repository navigation
v0.2.0
First release under the name dockza. This project is a fork of
docktui v0.1.1 by Achraf El Fadili,
continued independently after upstream development stopped. See
NOTICE for full attribution.
Fixed
- Crash on startup when any container publishes no ports. The daemon sends
Ports: null(rather than[]) for such containers, andtoContainerInfo
mapped over it unguarded — solistContainersthrew
Cannot read properties of null (reading 'map')and the Stacks and Containers
views showed nothing but the error.Ports,NetworkSettings.Networksand
Namesare now all null-tolerant. This affected every user with a portless
container; it predates the fork and was present throughout 0.1.x.
Security
- Bumped
dockerode4.0.2 → 5.0.1, clearing all known advisories in the
dependency tree (2 high inprotobufjs, 2 moderate inuuid;npm audit
now reports zero, with and without dev dependencies). dockerode 5.0.0's only
breaking changes are dropping itsuuiddependency and raising the minimum
Node version, both of which this project already satisfies.@types/dockerode
moves 3.3.x → 4.0.x to match.
Changed
- Renamed
docktui→dockza. The binary, the window title, the header
brand and the help-overlay title all now readdockza. Users ofdocktui
shouldnpm uninstall -g docktuiandnpm install -g dockza.app; there is no
automatic migration path, but no configuration or state is carried between
them, so nothing is lost. - The npm package is published as
dockza.app, notdockza. npm's
automated typosquatting filter rejects the plaindockzaname for being too
similar to the unrelateddoczpackage, so the published name matches the
project homepage instead. This affects the install command only — the
executable installed onPATHis stilldockza. - Repository moved to github.com/shandyba/dockza;
homepage is now dockza.app. - New logo and icon set under
assets/(logo.svgplus generated PNG, square,
favicon and apple-touch variants). The previous docktui logo has been removed
and is not carried into this fork. LICENSEnow carries the copyright notices of both the original author and
the fork maintainer, as MIT requires. ANOTICEfile records the fork's
origin, the former name, third-party dependency licenses and trademark
attributions, and ships in the npm tarball alongsideLICENSE.
Added
- Networks view — a fifth view (key
5, beneath Volumes) listing Docker
networks with driver, scope, short ID, attached-container count, creation
time, and an in-use / unused status badge. Pressdto delete an unused
network (confirm dialog); built-in (bridge/host/none) networks and
any network with attached containers are guarded against deletion, consistent
with the Images and Volumes views (a network is in use whenever a container is
attached, running or stopped). Attached-container counts are keyed by network
name (the stable identifier a container stores; a stopped container's endpoint
ID can go stale after a daemon restart), so the count agrees with the
Containers view.