Skip to content

Need to document the LocalRegistry MSBuild property for SDK container publish #45171

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

Closed
baronfel opened this issue Mar 8, 2025 · 0 comments · Fixed by #45909
Closed

Need to document the LocalRegistry MSBuild property for SDK container publish #45171

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

Comments

@baronfel
Copy link
Member

baronfel commented Mar 8, 2025

Type of issue

Missing information

Description

The LocalRegistry MSBuild property allows users to control which local container tooling they use when pushing to local sources. Currently it can be set to either Docker or Podman, and if the property is not set at all, the SDK will probe for the presence of docker or podman tooling.

Since it's common for podman tooling to be registered as docker (since they share may of the same commands), the SDK does a bit of probing to determine which tool to use. The algorithm is:

IF  'docker' and 'podman' both exist AND 'docker' is just an alias for 'podman' THEN use 'podman'
ELSE if 'docker' exists THEN use 'docker'
ELSE if 'podman' exists THEN use 'podman'
ELSE error

[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 - 417524

@dotnet-policy-service dotnet-policy-service bot added the ⌚ Not Triaged Not triaged label Mar 8, 2025
@gewarren gewarren self-assigned this Apr 3, 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
@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
CamSoper added a commit to CamSoper/dotnet.docs that referenced this issue Apr 23, 2025
@CamSoper CamSoper moved this from 🔖 Ready to 🏗 In progress in dotnet/docs April 2025 sprint project Apr 23, 2025
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in dotnet/docs April 2025 sprint project Apr 23, 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
Development

Successfully merging a pull request may close this issue.

3 participants