container-publish

Configures .NET 10 container publishing via dotnet /t:PublishContainer without Dockerfiles.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/Trossitec/dotnet-claude-kit --skill container-publish-trossitec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: container-publish
Source: https://github.com/Trossitec/dotnet-claude-kit/tree/main/skills/container-publish
Command: npx skills add https://github.com/Trossitec/dotnet-claude-kit --skill container-publish-trossitec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the hassle of writing and maintaining a Dockerfile by generating OCI-compliant container images directly from your .NET project, aligned with .NET 10’s container publishing workflow.

Core Features & Use Cases

  • Dockerfile-less containerization: Build images using dotnet publish /t:PublishContainer instead of Dockerfile authoring.
  • Production-ready image configuration: Configure ContainerRepository, ContainerFamily (including noble-chiseled variants), ports, env vars, and labels via MSBuild properties.
  • Registry publishing, multi-arch, and CI-friendly artifacts: Support pushes to registries, build multi-architecture indexes, and output tarballs for environments without a Docker daemon.

Quick Start

Run dotnet publish /t:PublishContainer --os linux --arch x64 to build a container image without writing a Dockerfile.

Frequently Asked Questions about container-publish

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

FAQPage Schema
How do I build .NET 10 container images without writing a Dockerfile?▼

Dockerfile-less container images for .NET 10 are built using the dotnet publish /t:PublishContainer command. This generates OCI-compliant images directly from your project, eliminating manual Dockerfile authoring.

Does Dockerfile-less .NET container publishing support multi-architecture images?▼

Yes, Dockerfile-less .NET container publishing supports building multi-architecture indexes. You can use dotnet publish with specific --os and --arch flags to target different platforms.

What are chiseled images and how do I configure them for ASP.NET Core containers?▼

Chiseled images are production-oriented minimal container images configured via the ContainerFamily MSBuild property. Setting this to noble-chiseled variants produces secure, reduced-size images for ASP.NET Core and .NET workers.

Can I push .NET OCI images to a registry without a Docker daemon in CI?▼

Yes, Dockerless CI environments can push .NET OCI images directly to registries and export tarball artifacts. This allows container scanning and publishing without requiring a running Docker daemon.

How do I set ports and environment variables for .NET containers using MSBuild?▼

Ports and environment variables for .NET containers are configured using MSBuild properties within your project file. The container publishing workflow reads these properties to apply safe defaults like non-root images during the build.