AGENT SKILL

agentos-image-builds

Build, test, and publish OCI images safely from an exact Git revision inside or outside an AgentOS Fleet. Use when a First or Second Mate needs an unreleased image, must choose BuildKit or Buildah for an in-cluster build, or needs to make an immutable image digest available to Kubernetes without a host runtime socket.

License 许可
MIT
所属仓库
akua-dev/agentos
最近更新
2026-11-09
Stars
★ 8
Forks
0

01 前言 Front Matter

name
agentos-image-builds
description
Build, test, and publish OCI images safely from an exact Git revision inside or outside an AgentOS Fleet. Use when a First or Second Mate needs an unreleased image, must choose BuildKit or Buildah for an in-cluster build, or needs to make an immutable image digest available to Kubernetes without a host runtime socket.

02 资源文件 1

03 SKILL.md 正文

Build Fleet images

  1. Resolve the exact committed Git revision, Dockerfile, target platforms, existing builder, target registry and node pull path. Stop on uncommitted source unless the Captain explicitly chooses a disposable local experiment that will not be represented as a release.
  2. Load $agentos-registry when no approved registry and node-reachable pull path already exist. Ask before credentials, registry creation, cluster mutation, cost or external exposure.
  3. Prefer an existing reviewed platform build service. For a new in-cluster path, start from the current official BuildKit Kubernetes examples and rootless guidance:
    • on a compatible Kubernetes and runtime, prefer a one-shot BuildKit Job with a Pod user namespace (hostUsers: false);
    • otherwise use rootless BuildKit only after its user-namespace, seccomp/AppArmor, snapshotter and storage requirements pass a lifecycle test;
    • use Buildah as a maintained alternative only where its unshare, UID/GID mappings and storage driver are verified.
  4. Discover the current supported builder version from official documentation or releases and pin its image by digest. Do not introduce archived Kaniko, mount a host Docker/containerd socket, or grant host-namespace privilege as a shortcut. Root inside a Pod user namespace remains unprivileged on the host and can still execute ordinary package-installing Dockerfile steps; verify host support rather than assuming it.
  5. Mount registry authentication through a reviewed Secret, workload identity or credential provider. Never place credentials in command arguments, image layers, build context or logs.
  6. Build the exact commit with native buildctl or buildah, push it, read the registry-confirmed digest and use only name@sha256:... for testing or deployment. Verify that the target kubelet can pull that digest before changing a Mate.
  7. Preserve build logs, source revision, builder identity and resulting digest as evidence. Roll out one Mate at a time and keep the previous digest available for rollback.

Treat vCluster shared nodes as host-node builds and pulls: the host runtime, filesystem and policy still determine support. The AgentOS image contains a portable shallow Git seed. When building from a linked worktree, use a remote Git context at the exact pushed commit with BuildKit's BUILDKIT_CONTEXT_KEEP_GIT_DIR=1 build argument instead of sending the worktree's host-specific .git indirection as a local build context. Set AGENTOS_GIT_REMOTE to the credential-free fork or project URL and keep AGENTOS_GIT_UPSTREAM on the public AgentOS upstream when appropriate.

04 同仓库更多 Skills

akua-dev
akua-dev/agentos

example-replacement

Reconcile the example replacement AgentOS distribution.

★ 8
akua-dev
akua-dev/agentos

example-additive

Inspect the example additive AgentOS behavior.

★ 8
akua-dev
akua-dev/agentos

agentos-upgrade

Upgrade one persistent AgentOS Mate or, from First Mate with exact Captain authority, every active persistent Mate in one Fleet to an exact published stable release, including its run-once released database migrations. Use for stable First- or Second-Mate updates, resumed post-replacement verification, and authorized rollback boundaries. Do not use for dogfood, Crewmates, provisioning, retired Mates, services, or another Fleet.

★ 8
akua-dev
akua-dev/agentos

agentos-supervision

Reconcile and supervise an AgentOS Mate's direct reports across PostgreSQL, Kubernetes, Herdr, PVCs, and Git. Use at every First- or Second-Mate session start, after restart or compaction, while delegated work is active, when Inbox or runtime state changes, and for blocked, stale, stuck, failed, interrupted, or recovering agents.

★ 8
akua-dev
akua-dev/agentos

agentos-secrets

Safely create, retry, rotate, take over, roll back, project, and revoke AgentOS-managed Kubernetes Secrets without retaining or printing credential bytes. Use whenever an AgentOS workflow moves credential files into Kubernetes, changes an existing managed Secret, verifies a projected credential, encounters conflicting Secret ownership or legacy annotations, or retires a Kubernetes-delivered credential.

★ 8
akua-dev
akua-dev/agentos

agentos-runtime

Inspect, create, and operate AgentOS runtime pods, Kustomize overlays, Herdr sessions, Mise toolchains, agent worktrees, terminals, PVCs, Kubernetes health, attach paths and runtime recovery. Use for normal First- or Second-Mate Kubernetes operations, child-Agent workload creation, tool resolution, stuck-agent debugging, remote terminal access, pod or session recovery, and readiness diagnosis.

★ 8