[martinothamar]

• ghcr.io/digdir/agentctl:v0.1.0-preview.13 does not exist yet. It now pins the release image's digest, sha256:5451dd5e…, instead of the main digest sha256:2374c65d… (823bac6268). The release commit 22f091c adds only the changelog on top of that main commit.

The dev Agent ran agentctl and agentd from digdir-agents main while it waited for a release with nested Sandboxes. Its manifests also mounted a tmpfs at /tmp, so large builds ran out of space in RAM. The 0.1.0-preview.13 changelog covers both: nested Sandboxes, and /tmp on the Sandbox disk (digdir/digdir-agents#329).

This PR:

• bumps the FROM digest of agentctl-base:ubuntu-26.04-desktop to sha256:762a7fd2… (ubuntu-26.04-desktop-sha-1e6d39dafd, .env makes a project no longer accessible. pingdotgg/t3code#329's merge commit). The previous digest was built before .env makes a project no longer accessible. pingdotgg/t3code#329.
• removes the /tmp tmpfs mounts from agent.yaml and agent.nested.yaml, as Temporary files in the base README describes.
• copies agentctl and agentd from ghcr.io/digdir/agentctl:v0.1.0-preview.13@… instead of :main@…, and rewrites the Dockerfile comment that said the image waits for a release.
• updates the README: the manifest needs agentctl 0.1.0-preview.13 or later, not a build from main.

Existing Agents keep their image and mounts. To pick up the change, save your work, then recreate the Agent.

Testing

• podman build agents/dev succeeds with the release digest. agent-image-check: ok, and agentctl --version in the image prints v0.1.0-preview.13.
• Before the release, with the main build (v0.1.0-preview.12.main.g823bac6) in the image, I applied the nested variant from a copy of agents/dev in a nested Agent, using this Sandbox's agentctl (main build 07b3ae5). The Agent became Ready, systemctl is-system-running reported running, and the fork was cloned with upstream added.
  • /tmp is ext4 on the 32Gi root disk. A 3 GiB file fit in it; the old 2Gi tmpfs could not hold that.
  • A Claude Code Session (Haiku, low effort) and a Codex Session (gpt-6-luna, low effort) each ran hostname (t3code-dev-nested) and reported /tmp as ext4.
  • After Stop and Start, the Agent was Ready again, both Sessions were Idle, /tmp had been cleared and /var/tmp kept its file. Then I deleted the Agent. I did not repeat this test with the release image, since only the version string changed.

Made by Claude Opus 5.5 in Claude Code, driven from T3 Code.