New docker images fail running apt-get update?

[bbimber]

Hello,

I recently tried updating one of our docker containers to use bioconductor_docker:RELEASE_3_10. When I ran "apt-get update", it fails with errors along the lines of the following. I think this has to do with the date being incorrect on the image?

Step 1/2 : from bioconductor/bioconductor_docker:RELEASE_3_10
---> 35e63c04aa52
Step 2/2 : RUN apt-get update -y
---> Running in 5a17e10abbf4
Get:1 http://deb.debian.org/debian buster InRelease [122 kB]
Get:2 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Get:3 http://deb.debian.org/debian buster-updates InRelease [49.3 kB]
Get:4 http://deb.debian.org/debian buster/main amd64 Packages [7,907 kB]
Reading package lists...
E: Release file for http://security.debian.org/debian-security/dists/buster/updates/InRelease is not valid yet (invalid for another 6d 2h 55min 29s). Updates for this repository will not be applied.
E: Release file for http://deb.debian.org/debian/dists/buster-updates/InRelease is not valid yet (invalid for another 7d 9h 38min 1s). Updates for this repository will not be applied.

This simple docker file is sufficient to repro, at least for me:

from bioconductor/bioconductor_docker:RELEASE_3_10

RUN apt-get update -y

[dlvergara]

You only need to restart Docker, the date of the docker engine is delayed.

[bbimber]

interesting - thanks for the quick reply. yes, that fixed it.