Can't get Helm to login to Project quay

99 views
Skip to first unread message

Alistair MacCallum

unread,
Oct 4, 2023, 5:54:35 AM10/4/23
to quay-sig
Hi all,

I've recently setup a quay instance from their github repo to test if it will work  for us as a container and helm repo. Currently I have it running in docker using the bundled docker compose file and then I have an nginx proxy in front of it to provide ssl. Everything is running smoothly so far as I can access the web ui and create users and repositories however when I try to login in with helm I get the following error.

WARN[0004] insecure registry https://quay.vaarst.net should not contain 'https://' and 'https://' has been removed from the insecure registry config
INFO[0004] Error logging in to endpoint, trying next endpoint  error="Get \"https://quay.vaarst.net/v2/\": error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: \"<!doctype html><html lang=\\\"en\\\"><head><title>HTTP Status 404 – Not Found</title><style type=\\\"text/css\\\">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 404 – Not Found</h1></body></html>\""
INFO[0004] Error logging in to endpoint, trying next endpoint  error="Get \"http://quay.vaarst.net/v2/\": error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: \"<!doctype html><html lang=\\\"en\\\"><head><title>HTTP Status 404 – Not Found</title><style type=\\\"text/css\\\">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 404 – Not Found</h1></body></html>\""
Error: Get "http://quay.vaarst.net/v2/": error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "<!doctype html><html lang=\"en\"><head><title>HTTP Status 404 – Not Found</title><style type=\"text/css\">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 404 – Not Found</h1></body></html>"

I have already set the FEATURE_GENERAL_OCI_SUPPORT flag to true in the true in the config file and I am using the login instructions from the doc here.

Can anyone point me in the right direction to get this working?

Thanks in advance!

Daniel Messer

unread,
Oct 4, 2023, 6:20:40 AM10/4/23
to Alistair MacCallum, quay-sig
It seems like our docs are missing the correct push command. While you only need to specify the registry's FQDN for the `helm login` command you need specify at least an organization when pushing a chart tarball as outlined in the Helm docs: https://helm.sh/docs/topics/registries/#the-push-subcommand

You didn't specify the helm command, that produces the error above, but from the error message it seems like that it is the push command failing.

--
You received this message because you are subscribed to the Google Groups "quay-sig" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quay-sig+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quay-sig/4489e8f3-17dc-4505-8b59-3479adb5c7e4n%40googlegroups.com.


--
Daniel Messer

Product Management

Red Hat OpenShift

Reply all
Reply to author
Forward
0 new messages