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
Pushing to library/xxx ends up creating URLs referencing only xxx, which then fails.
The issue appears to be in the current copy of the upstream github.com/docker/distribution / github.com/docker/docker code, but it's not clear whether updating those would solve the problem (and the update is non-trivial to perform).
(Note bits like DEBU[0018] Manifest list push url: https://registry-1.docker.io/v2/irssi/manifests/latest, which should be https://registry-1.docker.io/v2/library/irssi/manifests/latest instead, etc.)
We've managed to verify our assumptions with the following patch which simply forces the upstream code to use library/xxx for official images (which we're likely going to apply locally for continuing our builds while a proper fix to this problem is found), but this isn't a great long-term solution since it modifies code in vendor/ (and we cannot see a simple solution to this which doesn't do so):
ping @stevvooe or @dmcgowan: when you get a chance, could you let me know how push to library/ is handled in the docker client/engine? I assume there is some potential magic there which handles retaining the "library/" prefix when necessary on push..
Pushing to
library/xxx
ends up creating URLs referencing onlyxxx
, which then fails.The issue appears to be in the current copy of the upstream
github.com/docker/distribution
/github.com/docker/docker
code, but it's not clear whether updating those would solve the problem (and the update is non-trivial to perform).A full log of a failed push can be found at: https://gist.github.com/anonymous/20846e9e9aa995ddf2a6cfe72e1a4a42
(Note bits like
DEBU[0018] Manifest list push url: https://registry-1.docker.io/v2/irssi/manifests/latest
, which should behttps://registry-1.docker.io/v2/library/irssi/manifests/latest
instead, etc.)The associated YAML file:
We've managed to verify our assumptions with the following patch which simply forces the upstream code to use
library/xxx
for official images (which we're likely going to apply locally for continuing our builds while a proper fix to this problem is found), but this isn't a great long-term solution since it modifies code invendor/
(and we cannot see a simple solution to this which doesn't do so):The text was updated successfully, but these errors were encountered: