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

Unable to parse docker image manifests when populating package variables #9164

Open
tleed5 opened this issue Dec 10, 2024 · 0 comments
Open
Labels
kind/bug This issue represents a verified problem we are committed to solving

Comments

@tleed5
Copy link

tleed5 commented Dec 10, 2024

Severity

Non blocking

Version

Latest

Latest Version

I could reproduce the problem in the latest build

What happened?

We fail to parse manifest information from the dockerhub registry as returned API response is in a different schema, we are currently expect Image Manifest V 2, Schema 1 but the API returns Image Manifest V 2, Schema 2

Reproduction

Ensure verbose logging is enabled

  1. Create a docker hub feed
  2. Create a deployment process that references a official docker image e.g. nginx
  3. Deploy

Error and Stacktrace

Unable to extract labels from Image manifest so they will not be included in the deployment variables Sequence contains no elements
System.InvalidOperationException: Sequence contains no elements
   at System.Linq.ThrowHelper.ThrowNoElementsException()
   at System.Linq.Enumerable.First[TSource](IEnumerable`1 source)
   at Octopus.Core.Packages.Docker.DockerAdditionalVariablesContributor.ExtractManifestLabels(DockerFeed feed, String packageId, IVersion version) in /Users/travis/dev/OctopusDeploy/source/Octopus.Core/Packages/Docker/DockerAdditionalVariablesContributor.cs:line 78

More Information

Issue occurs here https://github.com/OctopusDeploy/OctopusDeploy/blob/e6f2c8085dcb27c5adc38242094fb786a12c79c1/source/Octopus.Core/Packages/Docker/DockerAdditionalVariablesContributor.cs#L77

Workaround

No response

@tleed5 tleed5 added the kind/bug This issue represents a verified problem we are committed to solving label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug This issue represents a verified problem we are committed to solving
Projects
None yet
Development

No branches or pull requests

1 participant