October-28th-2017, 06:27 AM
(This post was last modified: June-16th-2019, 07:27 PM by Armin@netPI.)
KWhenever an image is loaded from Docker Hub a certificate is exhanged between the device that pulls the image and the Docker site. This is because of security reasons. The certificate contains next to others also an information about when it was created and until it is valid. During the pulling process Docker Hub compares these times against its system time to release an image or not.
If now the expiration time - even if it is just a second - is in the past and signals the image certificate has expired an image cannot be loaded. So on netPI the same scenario happens if netPI's system time is not set up right and different to the actual time Docker Hub is referencing on ... an "image unavailable" message is reported in this case although available on Docker Hub. So make sure you manually set netPI's time correctly or setup an NTP server keeping an eye on the system time automatically.
If now the expiration time - even if it is just a second - is in the past and signals the image certificate has expired an image cannot be loaded. So on netPI the same scenario happens if netPI's system time is not set up right and different to the actual time Docker Hub is referencing on ... an "image unavailable" message is reported in this case although available on Docker Hub. So make sure you manually set netPI's time correctly or setup an NTP server keeping an eye on the system time automatically.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
