This commit solves this issue https://github.com/projectatomic/docker/commit/f4b87f52db74cf8f88a87fe61ba74cd8395edb69 Not sure whether it's already pushed and dnf can see it though Everything works fine building the latest projectatomic/fedora-1.9 branch
w/o that patch: $ docker push runcom/test1 The push refers to a repository [runcom/test1] (len: 1) unable to ping registry endpoint https://runcom/v0/ v2 ping attempt failed with error: Get https://runcom/v2/: dial tcp: lookup runcom: No address associated with hostname v1 ping attempt failed with error: Get https://runcom/v1/_ping: dial tcp: lookup runcom: No address associated with hostname w/ the patch: $ docker push runcom/test2 The push refers to a repository [docker.io/runcom/test2] (len: 0) ec97a2c1f2f6: Pushed c51f86c28340: Image already exists 039b63dd2cba: Pushed latest: digest: sha256:d05f72074e1b2f2e1f410fe54f9f85a01285f7f28122c362a5a06d18d639bed6 size: 4233 Tony ----- Messaggio originale ----- | Da: "Dusty Mabe" <du...@dustymabe.com> | A: atomic-devel@projectatomic.io | Inviato: Giovedì, 3 dicembre 2015 6:27:57 | Oggetto: [atomic-devel] Issues with docker push in 1.9 | | | In fedora the 1.9 docker rpm is out. I am having issues pushing to the | repo. | | If I push like I used to be able to: | | ``` | [root@f23 helloapache (master *=)]# docker push dustymabe/helloapache | The push refers to a repository [dustymabe/helloapache] (len: 1) | unable to ping registry endpoint https://dustymabe/v0/ | v2 ping attempt failed with error: Get https://dustymabe/v2/: dial tcp: | lookup dustymabe: No address associated with hostname | v1 ping attempt failed with error: Get https://dustymabe/v1/_ping: dial | tcp: lookup dustymabe: No address associated with hostname | ``` | | If I add docker.io in front: | | ``` | [root@f23 helloapache (master *=)]# docker push | docker.io/dustymabe/helloapache | | | | The push refers to a repository [docker.io/dustymabe/helloapache] (len: 0) | Repository does not exist: docker.io/dustymabe/helloapache | ``` | |
