On Tue, Dec 2, 2014, at 06:54 PM, Dennis Gilmore wrote:
Yes, I was thrown for a loop after downloading because the date is incorrect in the image: 20141102 when I presume 20141202 is right.
However *locally* I also had a "nightly" image with the correct date, but Adam Williamson tells me the nightly images don't have freeze exception packages.
I booted the "1102" image and it did have the right docker-io. So I guess the bottom line is things are OK, but we should really ensure the date is correct on the next run.