Closed mattdowdell closed 3 years ago
Apparently a known issue according to #1683
Thanks for all your contributions! This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Description
I'm setting up portus for my team wiuthin our company network. To get out of said network, we need a HTTP proxy. Because most docker builds require a proxy for installing external assets, e.g. installing RPMs from official repos, I use
~/.docker/config.json
to define a proxy and proxy exclusions. This was picked up by portus when trying to configure the initial registry causing confusing errors such as "Error: registry does not implement v2 of the API" while clearly using a v2 registry image.Steps to reproduce
~/.docker/config.json
I often find myself dealing with the proxy doing unexpected things, so I'm semi-used to it being a point of pain. That said, it would be nice to have some kind of toggle to use the configured proxy or not for contacting the registry. Jenkins starts off with no proxy (maybe that's a systemd thing) and allows you to configure one if needed if you'd like to follow that model. If there's no need for using a proxy in Portus ever, then I'm happy to be told to unconfigure my proxy and be on my way.
uname -a
reports the host OS after wondering whereapt
went. Installnslookup
to try to blame DNS. Installnmap
to cast blame on lack of open ports. Finally installcurl
and realise your foolishness.Relevant error message comes from here: https://github.com/SUSE/Portus/blob/c00c7c39d155018a47beded115b98601b20843ff/app/models/registry.rb#L132 Not much in the way of logs to help debug this further - you just have to intuit that a proxy is your problem.
Deployment information
Deployment method: docker-compose:
Configuration:
Portus version: 2.4.3@5a616c0ef860567df5700708256f42505cdb9952