radius-build-images

Build and push Radius container images from source to a registry.

1.7k|136|Updated Feb 20, 2021
One-click install
npx skills add https://github.com/radius-project/radius --skill radius-build-images
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: radius-build-images
Source: https://github.com/radius-project/radius/tree/main/.github/skills/radius-build-images
Command: npx skills add https://github.com/radius-project/radius --skill radius-build-images

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build and push Radius container images from source to a registry reachable by your Kubernetes cluster, enabling local development and testing without prebuilt images.

Core Features & Use Cases

  • Build multiple Radius images from source directories (deploy/images/...) as defined in the workflow.
  • Push built images to a registry, with support for multi-architecture builds and registry authentication.
  • Integrate with CI/CD pipelines via Make targets and DOCKER_REGISTRY/DOCKER_TAG_VERSION environment variables for predictable pushes.

Quick Start

Run the default make targets to build and push all Radius images to your registry.

Frequently Asked Questions about radius-build-images

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

FAQPage Schema
How do I build and push Radius container images from source to a local registry?

To build and push Radius container images from source, run the default GNU Make targets which compile the source directories and publish the images to your configured DOCKER_REGISTRY. You can control tagging using the DOCKER_TAG_VERSION environment variable.

What prerequisites do I need to build Radius images locally?

Building Radius images locally requires Docker, GNU Make, and Go installed on your system. You also need access to a container registry reachable by your Kubernetes cluster to push the built images.

Can I build multi-architecture Radius container images for Kubernetes?

Yes, multi-architecture builds of Radius container images are supported via Docker buildx. This allows you to create and push images compatible with different CPU architectures to your registry for local development and testing.

How do I customize container image tags when building Radius images in CI/CD?

You can customize container image tags in CI workflows by setting the DOCKER_REGISTRY and DOCKER_TAG_VERSION environment variables before running the Make targets, ensuring predictable tagging and push behavior for your pipeline.

Why build Radius images from source instead of using prebuilt images?

Building Radius images from source enables local development and testing without relying on prebuilt images. It allows you to apply custom changes, test workflows, and publish images directly to a registry accessible by your Kubernetes cluster.