![]() |
![]() |
Subject: | Error upgrading to 5.1.7 |
Author: | [Not Specified] |
Posted: | 2016-10-18 09:27 |
I am trying to upgrade from 5.1.2 to 5.1.7, but I'm having some issues.In the upgrade guide, it says:
Download the primary Docker image of Zenoss Core for this release. The download takes approximately 10-20 minutes.
docker run -it --rm -v /root:/mnt/root \ zenoss/core_5.1:5.1.7_1 rsync -a /root/5.1.x /mnt/root
So I run the command but it results in the following:
Unable to find image 'zenoss/core_5.1:5.1.7_1' locally
Pulling repository docker.io/zenoss/core_5.1
Error while pulling image: Get https://index.docker.io/v1/repositories/zenoss/core_5.1/images: unexpected EOF
Anyone have this error before or are able to assist
Thanks
Subject: | I noticed today that 5.1.8 is |
Author: | [Not Specified] |
Posted: | 2016-10-19 09:27 |
I noticed today that 5.1.8 is now available, with CC 5.1.9. However, I'm still having the same issue, this time regarding serviced:
Could not start isvcs: Failed to pull image zenoss/serviced-isvcs:v40.1: Error while pulling image: Get https://index.docker.io/v1/repositories/zenoss/serviced-isvcs/images: unexpected EOF
Note that I am only getting this error on my master host and not on either of my 2 resource hosts. I upgraded all 3 hosts about the same time to CC 5.1.9 via the upgrade guide this morning.
The resource hosts both start serviced just fine, and just wait on the master to start, but clearly I cannot get it to start on the master.
Subject: | This issue still remains. |
Author: | [Not Specified] |
Posted: | 2016-10-24 12:23 |
This issue still remains. Even when I simply run a docker pull command on the serviced-isvcs repository:
# docker pull zenoss/serviced-isvcs
Using default tag: latest
Pulling repository docker.io/zenoss/serviced-isvcs
Error while pulling image: Get https://index.docker.io/v1/repositories/zenoss/serviced-isvcs/images: unexpected EOF
Subject: | Figured it out... I had some |
Author: | [Not Specified] |
Posted: | 2016-10-27 10:30 |
Figured it out... I had some proxy settings in /etc/sysconfig/docker that was causing the issue.
< |
Previous Incorrect Syslog parsing for Alcatel-Lucent routers (7750 SR) |
Next Lock interfaces |
> |