serverless-registry-proxy
serverless-registry-proxy copied to clipboard
Question: how does AUTH_HEADER work ?
@ahmetb I've played around with this app and I can successfully configure it to proxy a public image from either Docker Hub or quay.io on my custom domain.
I've tried using the AUTH_HEADER
variable to expose private images (hosted on quay.io) to a non-authorized account but cound't get this to work. (my end goal is to have custom authorization handler).
What is unclear to me is should I set a value of
Basic XYZ
where XYZ is the base64 encoded value you can find in ~/.docker/config.json
or to some other value?
If you can explain how the authentication handshake happens between the client and the registry that would probably also help me.
Thanks.
The code should be pretty explanatory. I believe it's used for basic authentication.