Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add documentation for ContainerImageFormat Container Publishing flag #45176

Open
baronfel opened this issue Mar 9, 2025 · 0 comments
Open

Add documentation for ContainerImageFormat Container Publishing flag #45176

baronfel opened this issue Mar 9, 2025 · 0 comments
Assignees
Labels
dotnet-fundamentals/svc 📌 seQUESTered Identifies that an issue has been imported into Quest.

Comments

@baronfel
Copy link
Member

baronfel commented Mar 9, 2025

Type of issue

Missing information

Description

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.

[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

  • ID: a8539d30-07b2-29ff-8e9b-09d83bc066e5
  • PlatformId: 36de283b-4744-4f85-0ab2-e0ce83954d51
  • Service: dotnet-fundamentals

Related Issues


Associated WorkItem - 417523

@dotnet-policy-service dotnet-policy-service bot added the ⌚ Not Triaged Not triaged label Mar 9, 2025
@dotnetrepoman dotnetrepoman bot 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 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
@dotnet-policy-service dotnet-policy-service bot removed the ⌚ Not Triaged Not triaged label Apr 3, 2025
@gewarren gewarren self-assigned this Apr 3, 2025
@sequestor sequestor bot added 📌 seQUESTered Identifies that an issue has been imported into Quest. and removed 🗺️ reQUEST Triggers an issue to be imported into Quest. labels Apr 4, 2025
@CamSoper CamSoper assigned CamSoper and unassigned gewarren Apr 8, 2025
@CamSoper CamSoper added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 8, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dotnet-fundamentals/svc 📌 seQUESTered Identifies that an issue has been imported into Quest.
Projects
Status: 🔖 Ready
Development

No branches or pull requests

3 participants