You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In 8.0.405 and greater, users can set the ContainerImageFormat MSBuild property to either Docker or OCI to force the generated images to be that format.
Why does this matter? By default, the .NET Tooling infers the image format from the base image used. For example, the .NET Base images are of type application/vnd.docker.distribution.manifest.v2+json (which is a Docker-centric format). However, many modern container tools use or expect OCI image formats like application/vnd.oci.image.manifest.v1+json. To force the SDK to use one of these two formats (which are largely convertible without loss of information), users can use ContainerImageFormat to tell the tooling which to standardize on.
dotnetrepomanbot
added
the
🗺️ mapQUEST
Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it.
label
Apr 3, 2025
gewarren
added
🗺️ reQUEST
Triggers an issue to be imported into Quest.
and removed
🗺️ mapQUEST
Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it.
labels
Apr 3, 2025
Type of issue
Missing information
Description
In 8.0.405 and greater, users can set the
ContainerImageFormat
MSBuild property to eitherDocker
orOCI
to force the generated images to be that format.Why does this matter? By default, the .NET Tooling infers the image format from the base image used. For example, the .NET Base images are of type
application/vnd.docker.distribution.manifest.v2+json
(which is a Docker-centric format). However, many modern container tools use or expect OCI image formats likeapplication/vnd.oci.image.manifest.v1+json
. To force the SDK to use one of these two formats (which are largely convertible without loss of information), users can useContainerImageFormat
to tell the tooling which to standardize on.[Enter feedback here]
Page URL
https://learn.microsoft.com/en-us/dotnet/core/containers/publish-configuration
Content source URL
https://github.com/dotnet/docs/blob/main/docs/core/containers/publish-configuration.md
Document Version Independent Id
87603b1d-8af0-ecb0-fca2-aacd3d7ef5a0
Platform Id
36de283b-4744-4f85-0ab2-e0ce83954d51
Article author
@gewarren
Metadata
Related Issues
Associated WorkItem - 417523
The text was updated successfully, but these errors were encountered: