update-container-images

Name: update-container-images
Availability: InStock
Author: Microsoft

Update pinned Docker image tags in Aspire ImageTags.cs files.

6.2k|952|Updated Sep 25, 2023

Search Tags:#version compatibility #build validation #Aspire #docker images #container tag updates #registry queries #C# automation

Ready to run

npx skills add https://github.com/microsoft/aspire --skill update-container-images

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-container-images
Source: https://github.com/microsoft/aspire/tree/main/.agents/skills/update-container-images
Command: npx skills add https://github.com/microsoft/aspire --skill update-container-images

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the repetitive, error-prone work of periodically updating Aspire-pinned Docker image tags so the local orchestrator and deployment use the newest compatible container versions.

Core Features & Use Cases

Registry-backed tag discovery: Queries Docker Hub and OCI registries (MCR, GHCR, Oracle, Quay) to find available tags for each pinned image.
Version-compatible updates: Selects the newest compatible tag while preserving the original version format precision (e.g., M.m vs M.m.p vs vM.m.p) and avoiding “latest”/rolling tags.
Safe application with validation: Updates both the string literal and its XML remarks in each *ImageTags.cs file, then instructs building affected projects to ensure compilation.

Quick Start

Use the update-container-images skill to update container image tags in the aspire repository.

Frequently Asked Questions about update-container-images

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I update pinned Docker image tags in Aspire hosting integrations?▼

Updating Docker container tags in Aspire requires running the bundled UpdateImageTags.cs script first to produce a JSON report, using LLM analysis to select the newest compatible versions, then modifying *ImageTags.cs files and validating by building affected .NET projects.

How does version compatibility work when updating Aspire container tags?▼

Version compatibility for Aspire container tags works by preserving the original version format precision, avoiding derived or latest preview tags, and selecting the newest compatible release from Docker Hub, MCR, GHCR, Oracle, and Quay registries.

What's the best way to automate Docker registry queries for Aspire image updates?▼

Automating Docker registry queries for Aspire involves executing the bundled UpdateImageTags.cs script to discover available tags across MCR, GHCR, and Quay, outputting a JSON report for LLM-based version selection.

Does updating container images in Aspire require building .NET projects?▼

Yes, updating Aspire container images requires building affected .NET projects to validate compilation after modifying the string literal and synchronizing the XML remarks in each *ImageTags.cs file.

Can I use this approach to update all Aspire integration images at once?▼

Yes, you can perform a full image sweep to update all Aspire integration images at once, applying the update to every *ImageTags.cs file that contains both Registry, Image, and Tag fields using the discovered registry tags.

Why does the Aspire container update process skip latest and rolling tags?▼

The Aspire container update process skips latest and rolling tags to ensure version stability and predictability, selecting only explicitly versioned tags that preserve the original format precision of the pinned Docker images.