Back to Blog
When i push hero my images dont apear5/18/2023 Root 1329 956 0 Dec09 ? 00:00:00 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-eno16777736.pid -lf /var/lib/NetworkManager/dhclient Root 984 1 0 Dec09 tty1 00:00:00 /sbin/agetty -noclear tty1 linux Root 845 1 0 Dec09 ? 00:00:00 /usr/sbin/mcelog -ignorenodev -daemon -foreground Root 841 1 0 Dec09 ? 00:00:00 /usr/bin/python3 -Es /usr/sbin/firewalld -nofork -nopid Root 1 0 0 Dec09 ? 00:00:04 /usr/lib/systemd/systemd -system -deserialize 15 I’ve also tried the command docker commit dd09de55abc9 docker.io/username/fedora-23-httpd which seems to correct the proceeding / in the images list, but still generates the same message when attempting to push the image to docker hub.Ĭan anyone advise what i may be doing wrong here? V1 ping attempt failed with error: Get dial tcp: lookup username: No address associated with hostnameįrom other tutorials I have read my commands appear to be correct, but the output of the images command shows the repository name with a / at the start. Unable to ping registry endpoint v2 ping attempt failed with error: Get dial tcp: lookup username: No address associated with hostname Then when running docker push username/fedora-23-httpd i get the message: The push refers to a repository (len: 1) username/fedora-23-httpd latest 0b9b4d0b820e 21 seconds ago 468.5 MB REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE When i do this and check the image using docker images i get the output: # docker images What i have done done so far is run a fedora base image, make my changes and then commit the changed using docker commit dd09de55abc9 username/fedora-23-httpd When attempting to push the image to the docker hub registry it seems to try utilise my hub username as a private server address. I have built a docker image and have committed the changes, and am attempting to push the image to my public docker hub account.
0 Comments
Read More
Leave a Reply. |