You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the case of using a proxy (for example, the name of the proxy project is dockerhub -- docker.io), what can I do without adding an access proxy image to the path?
I must now visit harbor.test.com/dockerhub/rancher/rancher:latest, how can I remove the dockerhub prefix from the path for agent projects?
The text was updated successfully, but these errors were encountered:
xzxiaoshan
changed the title
I must now visit harbor. test Com/dockerhub/router/router: latest, how can I remove the dockerhub prefix from the path for agent projects?
I must now visit harbor.test.com/dockerhub/router/router:latest, how can I remove the dockerhub prefix from the path for agent projects?
Nov 13, 2022
xzxiaoshan
changed the title
I must now visit harbor.test.com/dockerhub/router/router:latest, how can I remove the dockerhub prefix from the path for agent projects?
I must now visit harbor.test.com/dockerhub/rancher/rancher:latest, how can I remove the dockerhub prefix from the path for agent projects?
Nov 13, 2022
Currently this feature is not supported, because dockerhub is a project name, also indicate that it is a proxy request to dockerhub, if you remove it from the command, it means pulling image from the local project rancher.
This issue is being marked stale due to a period of inactivity. If this issue is still relevant, please comment or remove the stale label. Otherwise, this issue will close in 30 days.
In the case of using a proxy (for example, the name of the proxy project is dockerhub -- docker.io), what can I do without adding an access proxy image to the path?
docker. io/rancher/rancher:latest ---> harbor.test.com/rancher/rancher:latest
I must now visit
harbor.test.com/dockerhub/rancher/rancher:latest
, how can I remove the dockerhub prefix from the path for agent projects?The text was updated successfully, but these errors were encountered: