smithery.ai

container-update-report

Update container digests and deploy affected hosts end-to-end.

First seen Mar 30, 2026

Installation

$ npx skills add https://smithery.ai

Summary

  • Update container digests and deploy affected hosts end-to-end.
  • Use when the user wants to check for container updates, update container digests, or deploy container changes.
  • Triggers on requests like "update containers", "check for container updates", "deploy container updates", or "run container-update-report".

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,255 B
  • docs SUMMARY.md 344 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Container Update Report

Update container digests and deploy affected NixOS hosts end-to-end.

Workflow

1. Update Container Digests

Run the update command to fetch latest container SHAs:

just update-container-digests

This updates apps/fetcher/containers-sha.nix with the latest digests from all registries.

2. Check What Changed

Check the diff to see which containers have updates:

git diff apps/fetcher/containers-sha.nix

Summarize changes in a table format:

  • Registry (docker.io, ghcr.io, lscr.io, etc.)
  • Container name and tag
  • Note: If no changes, inform user that all containers are up to date

3. Map Containers to Hosts

Search for container usage in .nix files:

# Search for specific container
grep -r "container-name" --include="*.nix" .

Key locations:

  • apps/*.nix - Application definitions
  • modules/nixos/host/*/ - Host-specific configurations

See [container-host-mapping.md](references/container-host-mapping.md) for known mappings.

4. Deploy Affected Hosts

Ask user which hosts to deploy, then deploy each:

just colmena <hostname>

Run deployments in parallel when hosts are independent. Verify success by checking output shows "Activation successful" and "All done!".

5. Report Summary

After deployment, provide a summary table:

Container Host Status
container:tag hostname ✓

Common Container Locations

Container Typical Host
postgres orgrimmar (woodpecker, resume), ironforge (paperless)
redis ironforge (paperless)
woodpecker-agent/server orgrimmar
paperless-ngx ironforge
reactive-resume, minio, chromium orgrimmar

Resources

See [references/container-host-mapping.md](references/container-host-mapping.md) for detailed container-to-host mappings.