Dotnet published container packages not showing in the repo page #86748
Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
We are publishing Docker containers with the label
org.opencontainers.image.source
set so that the packages will be associated with one of our GitHub repositories however this is not currently working in our setup.We are creating containers using a
dotnet publish
command outlined in Microsoft documentation here.Our .csproj file contains the following line:
<DockerImageLabels>org.opencontainers.image.source=https://github.com/our-org/our-repo</DockerImageLabels>
however when inspecting the image we see that the tag value actually gets published by Dotnet ashttps://github.com/our-org/our-repo.git
(note the additional .git at the end of the URL).Could the
.git
at the end of the URL be preventing the association of the package to our repository?Beta Was this translation helpful? Give feedback.
All reactions