container-publish

Publish .NET 10 projects as OCI images without a Dockerfile.

640|145|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/codewithmukesh/dotnet-claude-kit --skill container-publish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: container-publish
Source: https://github.com/codewithmukesh/dotnet-claude-kit/tree/main/skills/container-publish
Command: npx skills add https://github.com/codewithmukesh/dotnet-claude-kit --skill container-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dockerfile-less containerization for .NET apps using the .NET 10 SDK publishing features. Build production-ready images directly from dotnet publish /t:PublishContainer, avoiding Dockerfile maintenance and enabling multi-arch support with chiseled images.

Core Features & Use Cases

  • No Dockerfile needed: publish directly from the project to produce OCI-compliant images with MSBuild properties.
  • Production-ready configurations: define container settings in the .csproj for consistent builds and deployments.
  • Multi-arch and registries: generate images for multiple architectures and publish to container registries with simple commands.
  • CI/CD friendly: ideal for automated pipelines that skip Dockerfile maintenance while producing lean images.

Quick Start

Publish your app with dotnet publish /t:PublishContainer to build a production container image without 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 containerize a .NET app without a Dockerfile?

You can containerize a .NET app without a Dockerfile by using the .NET 10 SDK PublishContainer feature. This builds an OCI-compliant image directly from your project via dotnet publish, using MSBuild properties for configuration instead of maintaining a Dockerfile.

Can I build multi-architecture container images using dotnet publish?

Yes, dotnet publish with the PublishContainer target supports multi-arch builds. It generates lean, reproducible OCI-compliant images across multiple architectures, making it suitable for standard web apps, microservices, and background workers.

How do I configure container settings for .NET projects without Docker?

Container settings are configured directly within your .csproj file using MSBuild properties. This production-ready approach ensures consistent builds and deployments while eliminating the need to maintain separate Dockerfile configurations.

Does the .NET PublishContainer target support pushing images to container registries?

Yes, the PublishContainer feature supports publishing built OCI-compliant images directly to container registries. This is achieved through simple dotnet publish commands, streamlining CI/CD automated pipelines by skipping Dockerfile maintenance.

What are chiseled base images and can I use them with .NET containerization?

Chiseled base images provide a lean foundation for containers, and the .NET 10 SDK PublishContainer feature supports their usage. This workflow produces minimal, reproducible images directly from your project without requiring a Dockerfile.

Why should I use MSBuild properties for .NET containerization instead of Docker?

Using MSBuild properties for .NET containerization avoids Dockerfile maintenance and enables reproducible builds. It allows you to define container settings in your .csproj for consistent deployments and CI/CD-friendly multi-arch image generation.