When working within a Docker subdomain environment, the standard Set Me Up instructions may not be applicable. This knowledge base article guides using the repository name during the login process for Helm registry within the subdomain environment.
When attempting to log in to the HelmOCI registry using the login command provided on the "Set Me Up" page, you may encounter the following error.
Error logging in to endpoint, trying next endpoint error="login attempt to https://server.jfrog.io/v2/ failed with status: 400 Bad Request"
Error: login attempt to https://server.jfrog.io/v2/ failed with status: 400 Bad Request.
To overcome this error, it is necessary to use the repository name in the login command.
helm registry login server-<repositoryname>.jfrog.io
Replace <repositoryname> with the actual name of your repository.
For eg:
My server name is https://testing.jfrog.io
My OCI reponame is : helmoci
The login command should look something like
#helm registry login testing-helmoci.jfrog.io
This solution should resolve the login issue and allow you to perform Docker operations in the Docker subdomain environment