Dockplane 0.2.0-rc.3

Dockplane 0.2.0-rc.3

The third candidate for 0.2.0, and a bugfix candidate: no new features since
0.2.0-rc.1.

Everything here is one subject seen from several pages — which host a record
belongs to, and whether what is on the screen is happening now or is the last
thing anybody saw. Running the first candidate against a real deployment made
both questions hard to answer, and this release answers them.

0.2.0-rc.2 was not published as a release: publication stopped before any
artifact was built. This candidate carries the same product fixes.

Highlights

A host is named by the name you gave it. A machine enrolled more than once
leaves a host resource behind for every enrolment, and every one of them
reports the same system hostname. Hosts, agents, containers and stacks all
showed that one word, so six different machines read as one. The name you chose
now leads and the system hostname follows it, everywhere a host appears —
including the deployment dialog and the stack list. Nothing is merged and
nothing is deduplicated: they are separate hosts, and they look it.

Last known means last known, immediately. A host that stops answering marks
its readings as the last ones at once, because nothing is going to refresh
them. Its containers and its Compose projects now do the same. For the length
of the staleness window, one page used to show workloads as running beside a
host that already said it was offline.

A host's readings stay on its page. CPU, memory and disk are kept while a
host is offline, labelled with when they were reported, rather than dropped.

A container whose host went quiet still opens. It was reported as though
the container no longer existed, which sent people looking for a workload that
had not gone anywhere. Its page opens, its state is shown as the last one seen
rather than in the colour of a running workload, and it says when it was
observed.

Logs say what is missing. Opening the logs of a container on an offline
host says the live stream is unavailable, instead of reporting it as an
operation that was not carried out.

A stack on an offline host says what it can still do. Configuration and new
revisions can be saved; deploying waits for the host to come back. Only the
deployment controls mentioned this before, each in a tooltip.

Fields look like fields. Form controls are easier to make out before they
are focused, in both themes. Several were drawn without a border at all in the
dark theme, and the sign-in fields were drawn as a box around their label
rather than around the input.

Creating a container says which host it can use. Every host is listed, a
host whose agent is offline cannot be selected, and the reason is given before
the form is filled in rather than after it is submitted.

Security

No change from 0.2.0-rc.1. Stacks remain typed capabilities, no Compose file
or command string reaches a managed host, and a stack whose host state is
unclear is still blocked rather than guessed at. See
Security Model,
Agent Security and
Authentication.

Installation

Ubuntu 24.04, Ubuntu 22.04 or Debian 12, with Docker Engine and the Compose
plugin:

VERSION=0.2.0-rc.3

sha256sum -c SHA256SUMS
tar xzf "dockplane-$VERSION.tar.gz"
cd "dockplane-$VERSION"
sudo ./install-control-plane.sh --domain dockplane.example.com

Then sign in and add your first host. See
Installation and
Add a Host.

Upgrading

The installer is the upgrade: download the release, check it, unpack it, run
it. It takes a backup and validates it before anything changes, and stops if
either fails.

Upgrading from 0.2.0-rc.1 changes no schema. Upgrading from 0.1.0 migrates
it, as that release's notes describe. Either way, upgrade the control plane
first and the agents afterwards. See Upgrading.

Supported platforms

Control plane	Ubuntu 24.04, Ubuntu 22.04 or Debian 12, amd64
Managed hosts	Debian 12, Ubuntu 24.04 or Ubuntu 22.04 with systemd

Ports: 80 and 443 for browsers, 9443 for agents. The API and PostgreSQL are not
published. See Supported Platforms.

ARM64

experimental — built and inspected, not runtime-tested

Packages, binaries and images are produced for arm64 and inspected, and no
arm64 machine has run them. Use amd64 in production.

This is a release candidate

It is the 0.2.0 feature set with the first candidate's reporting corrected.
Deploy it where you can afford to restore a backup.

Known limitations

Unchanged from 0.2.0-rc.1. Read
Known Limitations before deploying. In
short: applying a revision recreates every service, so a stack is briefly down
while it is rebuilt; deleting a stack leaves its networks and its named volumes
behind; a Compose project discovered on a host still cannot be taken over; a
stack secret cannot be read back; backups are not encrypted by Dockplane; and
images are not signed.

License

AGPL-3.0-only. See LICENSE.