Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I0930

The real image runs under the real limits before anything is deployed

Where it stands

devtask.issue
Readiness
blocked 3 of its dependencies are not DONE
Status
BLOCKED
Can start
not now
Milestone
fly-deployment
Milestone status
ACTIVE
Wave
5
Waiting on
I0906I0909I0912
Holds back
I0922I0923I0928I0931
Behind it in all
6
Evidence
0 of 4
In the waySubjectDetail
issueI0906I0906 is not DONE
issueI0909I0909 is not DONE
issueI0912I0912 is not DONE

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I0930

majordomus plan verify I0930

majordomus plan done I0930

What it is

Objective
Build the actual production image and run it under the resource limits of the cheap profile, verifying the process, its user, its port and its routes without fixed ports and without sleeping.
Why
Everything before this is a claim about an image. Running it under the limits it will actually face is the first evidence that the deployment can work, and it is far cheaper to learn here than after a deploy.
Now
No image and no container test exist.
Wanted
One test builds the production image, runs it constrained, polls readiness with a bounded timeout, and asserts the behaviour the deployment depends on.
Done when
unknown: the record declares no `completion`
Risk
A container test needs a container runtime, which not every environment has. It must skip explicitly and visibly where the runtime is absent rather than passing quietly.

Acceptance

  • The image under test is the production image, built by the canonical build
  • It runs under the declared memory and CPU limits of the cheap profile, and with a read-only filesystem where the application permits it
  • The process stays alive, its user id is not zero, and it listens on the declared port
  • Liveness and readiness answer, and the landing, documentation, API document and static assets are served
  • Readiness is reached by bounded polling on an ephemeral port, with no sleep and no fixed port
Validation
bash test/run.sh
Evidence required
image_builtconstrained_runroutes_passuid_nonzero
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
test/cases
Not
A fixed host portA sleep standing in for readinessA test image that differs from the production one
Depends on
I0906I0909I0912
Priority
p0
Profile
implementation
Parallel safe
true
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-09-06
Updated
2026-09-06
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.