container-publish

You can containerize a .NET application without a Dockerfile by using the .NET 10 SDK's PublishContainer MSBuild target. Running `dotnet publish /t:PublishContainer --os linux --arch x64` generates an OCI-compliant container image directly from your project file.

Yes, you can push multi-architecture .NET container images directly to a registry. By configuring ContainerRepository, ContainerImageTags, and runtime identifiers in your project, the PublishContainer target handles building and pushing the correct architectures.

Chiseled container images, like the `noble-chiseled` family, reduce attack surface and shrink image size by removing unnecessary OS components. You can select them for your .NET application by setting the ContainerFamily MSBuild property in your project file.

No, you do not need Docker installed to build and publish .NET container images. This dockerless approach uses the .NET 10 SDK's built-in PublishContainer MSBuild target to create OCI-compliant images and push them directly to a registry.

Required MSBuild properties for .NET container publishing include ContainerRepository, ContainerFamily, ContainerImageTags, and ContainerArchiveOutputPath. You must also enforce Linux targeting and configure proper authentication credentials before pushing to a registry.

You can export a .NET container image as a local tar archive by setting the ContainerArchiveOutputPath MSBuild property during the publish process. This allows you to generate the OCI-compliant image locally without immediately pushing it to a remote registry.