v2.0.2

The ingress proxy's ports and Let's Encrypt email can now be changed after ingress is turned on.

docker compose pull && docker compose up -d

Improved

• Ingress settings: a Settings button on the Ingress page (and a Change link next to the ports) opens one place for the HTTP and HTTPS ports, the Let's Encrypt email and the test environment. Before, the ports chosen when turning ingress on were fixed, and the email was hidden in a menu.
• Changing ports safely: Docker can't change a running container's ports, so the proxy is replaced. Routes are down for a few seconds, the old proxy is kept until the new one is up, and if a port is already in use the proxy stays on its current ports with a clear message. Port changes are listed under Activity.

Full Changelog: v2.0.1...v2.0.2

v2.0.1

A security update. A Trivy scan of the 2.0.0 image found 14 critical and 59 high vulnerabilities, almost all in libraries Docker Manager is built with. In 2.0.1 none are critical. The 6 high ones left are inside Docker's own buildx and compose plugins and clear when Docker publishes fixed builds.

docker compose pull && docker compose up -d

Security

• Spring Boot 4.0.1 to 4.0.9, which brings fixed versions of Tomcat, Spring Framework, Spring Security, Netty and Jackson.
• Bouncy Castle 1.86, Guava 33.8.0, and Apache HttpClient 5.6.5 with HttpCore 5.4.4. These were pulled in at vulnerable versions by the Docker client library.
• Ubuntu security updates are installed when the image is built.

Improved

• Security page: clicking a scanned image opens its vulnerabilities, each one says where in the image it was found (Java libraries, system packages or a specific program), and findings in Docker Manager's own image explain that updating Docker Manager fixes them.

Fixed

• Imported stacks said "Not deployed yet" on the Stacks page although they were running. They now say they were imported and haven't been redeployed from Docker Manager yet.

Full Changelog: v2.0.0...v2.0.1

v2.0.0

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

v1.0.2

What's Changed

• fix(header.js): remove close button functionality by @christolis in #1
• fix: use BASE_URL for CORS and fix healthcheck endpoint by @ankitsmt211 in #3

New Contributors

• @christolis made their first contribution in #1
• @ankitsmt211 made their first contribution in #3

Full Changelog: v1.0.1...v1.0.2

v1.0.1

Fixes:

• Add default SSL route in nginx to prevent fall over

Full Changelog: v1.0.0...v1.0.1

v1.0.0

What's Changed

Release first stable version of WDM.

v0.5.2

Full Changelog: v0.5.1...v0.5.2

v0.5.1

Full Changelog: v0.5.0...v0.5.1

v0.5.0

Full Changelog: v0.4.0...v0.5.0

v0.4.0

Full Changelog: v0.3.0...v0.4.0