Skip to content

v2.0.0

Choose a tag to compare

@surajkumar surajkumar released this 11 Nov 09:42
· 15 commits to main since this release

Docker Manager 2.0 is a rebuilt interface with three new areas: PostgreSQL databases, a private image registry, and security scanning.

docker pull wannaverse/docker-manager:2.0.0

Upgrading from 1.x? Back up the docker_manager_data volume and read Upgrading from 1.x first. In short: keep your own ENCRYPTION_KEY if you set one, add the two /opt/docker-manager/... mounts, and expect everyone to sign in once.

New

  • Databases: PostgreSQL 16, 17 and 18 servers with secure defaults (random administrator password, SCRAM-SHA-256, no published port, own network, every database closed to other users). SQL console, users and per-database access, scheduled backups with retention, restores with a safety backup first, copies to S3-compatible storage, and import from the PostgreSQL containers you already run.
  • Private registry: the official registry:3, over HTTPS through ingress with Let's Encrypt or on the server only, with its own users, browsing, tag deletion and space reclaiming. It is added as a sign-in automatically so deployments can pull from it.
  • Security: image scans with Trivy or Docker Scout, host checks with Docker Bench for Security (CIS Docker Benchmark), and one-click container fixes that you confirm first and can undo from History.
  • New interface (Next.js), with pagination, bulk actions, and progress shown for every action.
  • Stacks: import compose projects started elsewhere (all at once, without restarting them), versions you can return to, and sorting.
  • Ingress: sign-in pages with per-route users, optional Basic authentication, and a port picker.
  • Remote hosts over TLS or SSH.
  • Volume browser: read-only by default, with uploads, downloads and a write mode.
  • Logs open first on a container, with copy and download.
  • Redesigned email notifications (HTML with a plain-text version).

Fixed

  • Data-loss, upgrade and security issues found in a full review, including safer container recreation that puts the original back if the new container doesn't start.
  • Changing or removing a container's memory limit failed when one was already set.
  • Undo in History didn't restore security options or the process limit, and failed for older changes once the container had been replaced.
  • Health issues that had been resolved could come back.
  • Unknown pages returned status 200.
  • The app now shows the release version instead of "dev".

Full Changelog: v1.0.2...v2.0.0