Public Docker Hub OCI registry Feed Package search does not work in the Feed save and test or in an Octopus Step

[Clare-Octopus]

Severity

Not blocking customers but its confusing when they try and package search in the feed test and find no packages and also confusing in the step when they try and find a package.

Version

2024.2.9391 / 2024.3.10989

Latest Version

I could reproduce the problem in the latest build

What happened?

You will now need to authenticate to Docker Hub Public Repositories by following the workaround in this GitHub issue first if you are not using Username/Password in your OCI Registry Public Docker Hub external feed otherwise you will encounter an authentication issue when trying to deploy.

If you do have the feed setup correctly (considering the bug above) and are using a PAT and your DockerHub username for the external feed when you try and test the feed and search for a package that does not work and brings back no packages:

When you then try and search for the package in a step (Deploy a Helm chart) it does not find a package:

Note, if you manually enter the repository and package name into the step (ie if using our Octopus Helm Chart you need to type octopusdeploy/octopusdeploy-helm) you will be able to create a release, find the package version and deploy successfully, its just the searching endpoint that is an issue here.

Reproduction

1. Ensure you have a username and PAT in your OCI Registry Docker Hub Feed by following the workaround in this GitHub issue (if you have no username/pw in there already - the password needs to be a PAT).
2. Test the feed and type the repository and package name in (ie if using our Octopus Helm Chart you need to type octopusdeploy/octopusdeploy-helm).
3. Create a new project and include a Deploy a Helm Chart Step.
4. For the Chart Package action in that step chose the OCI Registry Feed from Step 1.
5. Physically type the repository and package name in (ie if using our Octopus Helm Chart you need to type octopusdeploy/octopusdeploy-helm).
6. See there are no results found.
7. Save the step with the repository and package name inputted manually and create the release, see it finds the package and versions.
8. You should be able to deploy successfully.

Error and Stacktrace

N/A

More Information

Initial customer ticket (internal) - https://octopus.zendesk.com/agent/tickets/200053 R and D (internal) - https://octopusdeploy.slack.com/archives/CNHBHV2BX/p1724319338369569

Workaround

No workaround required, you will just have to manually enter the repository and package name into the step (ie if using our Octopus Helm Chart you need to type octopusdeploy/octopusdeploy-helm) and save that.

The search function for the feed will not work.

[martinisaksen]

Any progress on this? We are using helm charts from Bitnami and they have now defaulted all new versions to their OCI registry on Docker. I spent a lot of time trying to set up the feed correctly because when I tried to test the configuration, no packages were returned. This bug wasted a lot of our time.

[Clare-Octopus]

Good morning @martinisaksen thank you for reaching out and I do apologise you have been affected by this bug. Funnily enough our engineer contacted me (as I initially raised this issue) before the holiday break and we were discussing ways forward for this.

Unfortunately, docker hub OCI registries do not support feed searches in general (limitation of OCI feeds in docker hub), so we are unable to completely fix this issue.

However, we are in the process of putting some feedback in place in the UI which will warn users of this fact and that should hopefully help inform our customers that the package should still be found on the create release page even though it is not found in the step itself. This has not been completely finalised yet but it will look something similar to this:

I was in discussions with the engineer about the wording of the warning as it needs to allude to the fact the step itself wont find the package in the dropdown but if fully typed in the step it will find it on a create release.

Hopefully, that does help future customers that run into this issue, and again, I am sorry you ran into it, and it took some time to diagnose before finding this public issue.

Kind Regards, Clare