Elyra
Elyra The coding agent eTerm The terminal that knows where each command ends Huskarl AI colleagues on your own Mac Starf An activity monitor for Apple silicon that never invents a number etrans An SSH and SFTP client for macOS Elyra VM Virtual machines for macOS, Linux and Windows on your Mac Litr A small, native web browser for macOS Notr A notebook for macOS e The native code editor Elyra Grove Native local development environment Askr The real server for Laravel & PHP Elyra Framework Rust + Svelte 5 framework for desktop apps Elyra Conductor Local project conductor Refr Local-first PDF workspace for macOS Elyra Workspace A desktop workspace for coding agents eDock A container runtime for the Mac Elyra SQL Server MySQL-compatible SQL server in Rust Elyra Félagi Agents as teammates on one board Elyra SQL Client Native desktop SQL workbench Elyra SQL Anywhere Replication-ready SQL engine Elyra Sjá SEO & GEO workspace for macOS Elyra DataGrid Server-driven data grid for Laravel
Release notes
Release notes
Elyra

Builds

Builds lists each docker build on eDock, newest first, from BuildKit's own history. Builds made with eDock's builder show up after Engine › Command line › Set up, which creates the edock-build builder.

Column
Build Its name: the tag, or the folder it was built from
Status Completed, Running, Error or Canceled
Steps How many, and how many came from the cache
Took How long it ran
Started When

Click a build to see:

  • Its steps, in the order they ran, each with its time and a cached badge when the cache had it. Click a step for its log.
  • Why it failed, at the top: the error, the step, and the Dockerfile lines around it. The failed step's log is opened for you.
  • Warnings from the Dockerfile checks, with the line and a link to more.
  • The image it made, for a completed build: its size, and how much bigger or smaller it is than the last build of the same name (green when it shrank). Inspect image opens it on the Images page, with its layers, and Scan opens its vulnerability scan. Once the tag has moved on to a newer build, the older build's image has no name to open.

Remove takes a build off the history. Its image, if it made one, stays.

Reading the history wakes the builder (and the VM), so the app reads it only while this page is open. Refresh reads it again.

From a terminal:

edock builds                    # the history, as JSON
edock builds show BUILDER ID    # one build
edock builds layers BUILDER ID  # the image it made: its size and layers
edock builds rm BUILDER ID