Skip to content

eDock 0.3.0

Choose a tag to compare

@kwhorne kwhorne released this 14 Nov 19:29
· 32 commits to main since this release

eDock 0.3.0 brings out much of what eDock's engine could already do.

Ports that just work

  • Every running container has an address at eDock's router, http://<name>.edock.localhost (or <service>.<project>… for Compose). It shows in the list and the menu bar, and reaches the container's web port even when nothing is published.
  • See what a container really listens on. The new Ports tab finds ports it listens on that nothing publishes (you forgot -p, or the image never declared them) and publishes them with one click, while it runs. You can also add, change or remove ports there.
  • Edit the environment in place. Inspect › Environment › Edit restarts the container with the new variables, and keeps its files.
  • Trusted HTTPS. Engine › Domains › Trust HTTPS gives https://<name>.edock.localhost a padlock. The certificates can only vouch for eDock's own names. Another server on ports 80 and 443? Give eDock's domains ports of their own there.

Linux machines

A new Machines page: long-lived Linux environments with your Mac user, passwordless sudo, and /Users at the same path.

  • Ubuntu, Debian, Alpine, Fedora, Arch, Rocky or openSUSE, optionally with systemd.
  • Ready in seconds, with a shell a click away.
  • From the terminal: edock machine shell <name>.

Image security

Click an image:

  • Layers: what each Dockerfile line added, and which lines came with the base image.
  • Security: known vulnerabilities, found by Grype straight from eDock's store, without starting the VM.
    • Findings by severity, with the versions that fix them and the line that brought them in.
    • Fixable only filter, earlier scans, and the SBOM as CycloneDX.
    • The first scan downloads the scanner and its database: about 200 MB, and about 3 GB on disk.

Engine settings

The Engine page has tabs now:

  • Resources: the VM's CPUs and memory, and what the containers, the VM and eDock itself use now.
  • Domains: container domain ports and HTTPS trust.
  • Builds & import:
    • docker build's cache size, and emptying it;
    • import from OrbStack or Docker Desktop (only read; containers arrive stopped);
    • a diagnostics report, saved where you choose.

Also

  • edock tls status | trust | untrust on the command line.
  • Cards everywhere lay out their content properly.

Download

eDock-0.3.0-arm64.dmg: Apple silicon, macOS 14 or later. Signed with a Developer ID and notarized by Apple. Download it from elyracode.com/edock, or below.

eDock 0.2.0 and later offer this update by themselves. Afterwards, press Restart engine on the Engine page.

Credits

eDock's engine is a fork of Kiri by Canestack Labs and the Kiri contributors, under Apache-2.0. The guest Linux kernel is GPL-2.0; its source is attached to this release.