Update - after re-examining the documentation for option 2 above (Docker Repository Reverse Proxy Strategies – Sonatype Support) I realized the reverse proxy was not setting the path correctly which was part of the issue.
so now the path is set to “/repository/dockerproxy/#{path}”
This results in the following on a docker pull:
Using default tag: latest
Error response from daemon: Head
https://nexus.mydomain.com:443/repository/dockerproxy/v2/ubuntu/manifests/latest: error parsing HTTP 404 response body: invalid character ‘<’
So that path actually looks correct and if I run it through postman or a browser it pulls things and gives me back some json. But for some reason when I run it through docker pull it throws the error. Which makes me think docker is doing something with headers that postman or the browser is not doing
Any ideas? I feel like we are really close here?