Skip to content

features: healthchecks, Compose build and conditions, bind volumes; two build known issues - #361

Open
cloudlabworks wants to merge 2 commits into
libracoder:mainfrom
cloudlabworks:docs-features-builds-compose
Open

cloudlabworks wants to merge 2 commits into
libracoder:mainfrom
cloudlabworks:docs-features-builds-compose

Conversation

@cloudlabworks

Copy link
Copy Markdown

Two commits, both in docs/features.md; happy to split them.

What works (first commit). These work on Kiri 0.2.1 and were not listed:
--health-* healthchecks (including --health-start-interval) and
ps --filter health=; Compose up --build and --wait, build:,
healthchecks, depends_on conditions (service_healthy,
service_completed_successfully), platform:; and local volumes that bind a
folder with driver_opts: {type: none, o: bind, device: /path}. Each was
checked on Apple silicon (macOS 27.0.1, Kiri 0.2.1): healthy/unhealthy/timeout
states and the health filter; a Compose project with build:,
up -d --build --wait, service_healthy and a bind volume; a
service_completed_successfully dependency with a platform: linux/amd64
service (uname -m gave x86_64).

Known issues (second commit):

  1. docker build --platform linux/amd64,linux/arm64 (Kiri's builder loads
    by default) fails with docker exporter does not currently support exporting manifest lists; --load too. -o type=oci,dest=image.tar
    works. Kiri's docker load does not read that archive
    (not an image archive: no manifest.json), so the entry says to build one
    platform at a time to use the image in Kiri.
  2. A build whose BuildKit cannot reach the registry says not found (details
    and the check to run are in the Linux: containers have no DNS on the default bridge; Compose/BuildKit builds can't resolve a digest-pinned base; bun install gets ConnectionRefused #330 comment). Reproduced on the Mac with
    no DNS in the builder, for a tag Kiri doesn't hold and for a digest-pinned
    base right after docker pull; with DNS restored the same builds pass.

AndreKurait added a commit to AndreKurait/asagiri that referenced this pull request Nov 16, 2026
Adapt public Kiri PR #361 while retaining Asagiri's built-in Docker
driver. Distinguish single-platform image loading from OCI output
through a docker-container builder, and describe local mirror versus
registry resolution. Keep the remaining runtime qualification gaps
beside the feature and test descriptions.

Adapted from libracoder/kiri#361
Public source: 184c594bde99bd30e6653f268982427cc05313bb

Co-authored-by: Andre Kurait <akurait@amazon.com>
Signed-off-by: Andre Kurait <akurait@amazon.com>
… volumes

These work on Kiri 0.2.1 and were not listed: --health-* options
(including --health-start-interval) and ps --filter health=; Compose
up --build and --wait, build:, healthchecks, depends_on conditions
(service_healthy, service_completed_successfully) and platform:; and
local volumes that bind a folder with
driver_opts: {type: none, o: bind, device: /path}.

Checked on Apple silicon, macOS 27.0.1, Kiri 0.2.1:
- healthy, unhealthy and timeout states, and the health filter
- a Compose project with build:, up -d --build --wait, service_healthy
  and a bind volume
- a service_completed_successfully dependency on a platform: linux/amd64
  service (uname -m gave x86_64)

Docs only. e2e coverage for these is proposed separately in libracoder#358.
1. docker build --platform linux/amd64,linux/arm64 (Kiri's builder loads
   by default) fails with "docker exporter does not currently support
   exporting manifest lists"; --load too. -o type=oci,dest=image.tar
   works, but Kiri's docker load does not read that archive
   ("not an image archive: no manifest.json"), so the entry says to build
   one platform at a time to use the image in Kiri.

2. A build whose BuildKit cannot reach the registry fails with
   "<image>: not found", because Kiri's mirror is asked first and its 404
   is the error BuildKit reports. Say so, and how to check the network
   instead. Reproduced on Apple silicon (macOS 27.0.1, Kiri 0.2.1) with no
   DNS in the builder, for a tag Kiri doesn't hold and for a
   digest-pinned base right after docker pull; with DNS restored the same
   builds pass. Mechanism and the check to run are in libracoder#330.

Refs libracoder#330
@cloudlabworks
cloudlabworks force-pushed the docs-features-builds-compose branch from 184c594 to c975769 Compare November 16, 2026 22:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant