container-update-report

Container Update Report

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "container-update-report" with this command: npx skills add fred-drake/nix/fred-drake-nix-container-update-report

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.

  1. 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

  1. 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 for known mappings.

  1. 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!".

  1. Report Summary

After deployment, provide a summary table:

Container Host Status

container:tag hostname ✓

Common Container Locations

Container Typical Host

postgres woodpecker, paperless, sonarqube, resume

redis paperless

woodpecker-agent/server woodpecker

n8n n8n

paperless-ngx paperless

Resources

See references/container-host-mapping.md for detailed container-to-host mappings.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

provision-nixos-server

No summary provided by upstream source.

Repository SourceNeeds Review
General

infrastructure

No summary provided by upstream source.

Repository SourceNeeds Review
General

nix

No summary provided by upstream source.

Repository SourceNeeds Review
General

nix

No summary provided by upstream source.

Repository SourceNeeds Review