# Publish .NET Containers Without Dockerfiles

Maintaining Dockerfiles adds work to standard .NET application releases. This skill guides SDK container publishing through project settings, registry commands, and CI examples.

## Install

```bash
npx skillstore add codewithmukesh/container-publish
```

## Metadata

- Status: approved
- Slug: codewithmukesh-container-publish
- Skillstore revision: r1
- Version status: missing
- Tree hash: ae249560ef9f7719d22999c056318c6d7699032ca0cd4dd34e67adc4edcb1cb1
- Author: codewithmukesh
- GitHub username: codewithmukesh
- License: MIT
- Repository: https://github.com/codewithmukesh/dotnet-claude-kit/tree/23300897f4d1a276bc475e373ecfe886e43dd7c5/skills/container-publish
- Ref: f7b161679d1208226f24d167acf8573bb901d0ee
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, env\_access
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/codewithmukesh-container-publish
- Manifest: https://skillstore.pages.dev/api/skills/codewithmukesh-container-publish/manifest

## Capabilities

- Provides PublishContainer commands and MSBuild settings for repositories, ports, environment variables, and image labels.
- Shows authentication and publishing examples for GitHub Container Registry, Azure Container Registry, and Docker Hub.
- Explains Linux x64 and ARM64 image configuration and multiple image tags.
- Demonstrates container archive output and a Trivy image scanning command.
- Compares chiseled image families, localization requirements, and Native AOT settings.
- Provides a GitHub Actions publishing example and a decision guide for SDK publishing versus Dockerfiles.

## Use Cases

- Containerize an ASP.NET Core API: Configure a .NET 10 API for Linux container publishing with a chiseled image and explicit application ports.
- Prepare Registry Publishing in CI: Adapt the GitHub Actions example to authenticate with GitHub Container Registry and publish images tagged with commit identifiers.
- Review Container Build Choices: Compare image families, architecture targets, archive scanning, and custom base image needs before selecting a publishing approach.

## Prompt Templates

### Start With Local Publishing

```
Show the minimal command to publish my .NET 10 API as a Linux x64 container. Explain the local tooling prerequisites.
```

### Configure a Production Image

```
Suggest project settings for my .NET 10 API using noble-chiseled, repository acme/orders, and port 8080. Check whether localization requires another image family.
```

### Add Registry Publishing to CI

```
Draft a GitHub Actions job to publish my .NET 10 API to ghcr.io with commit tags. Explain authentication and permissions before any publishing.
```

### Plan Multiple Architectures and Archive Scanning

```
Plan Linux x64 and ARM64 SDK container publishing for my service. Include a separate archive scanning workflow and assess custom base image needs.
```

## Limitations

- Contains documentation and examples, not bundled build tools or automated validation scripts.
- Requires the .NET SDK and appropriate registry credentials; local daemon publishing and archive scanning need additional tools.
- SDK container publishing cannot install operating system packages; use a prepared custom base image or a Dockerfile.
- Does not provide an SDK publishing workflow for Azure Functions or guarantee application compatibility and image sizes.

## Best Practices

- Choose an appropriate chiseled image, preserve non-root execution, and verify localization and native dependency requirements.
- Confirm registry destinations and use scoped credentials before publishing images.
- Specify Linux architecture targets, use traceable image tags, and scan archive output before release.

## Anti Patterns

- Using deprecated ContainerImageName settings or relying on the older DefaultContainer publish profile.
- Publishing without registry authentication or without checking the target operating system and architecture.
- Expecting SDK container publishing to execute package installation commands or replace every Dockerfile workflow.

## Security Audit

- Audited at: 2026-10-31T14:11:35.452\+00:00
- Summary: All 48 static findings are false positives: 47 match Markdown backticks, and one references a GitHub Actions token for registry authentication. Commands and credentials support the documented container publishing workflow. No evidence found of prompt injection, credential exfiltration, or malicious execution.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0