Missing Image Creation Date Metadata

[nebhale]

Currently, when I create an image using pack build, the docker image command reports that the image is 292 years old (last line):

hypnotoad: docker images
REPOSITORY                      TAG                 IMAGE ID            CREATED             SIZE
golang                          latest              d817ad5b9beb        5 days ago          774MB
packs/run                       0.0.1-rc.259        13df6da62128        2 weeks ago         160MB
localhost:5000/run              0.0.1-rc.259        13df6da62128        2 weeks ago         160MB
localhost:5000/run              0.0.1-rc.258        54413ee93b68        2 weeks ago         160MB
packs/run                       0.0.1-rc.258        54413ee93b68        2 weeks ago         160MB
localhost:5000/builder          <none>              f6bc8ff8a841        2 weeks ago         674MB
localhost:5000/builder          latest              ac7e0fa41e38        2 weeks ago         674MB
packs/build                     latest              8b41724a4c36        2 weeks ago         160MB
localhost:5000/build            latest              8b41724a4c36        2 weeks ago         160MB
registry                        latest              2e2f252f3c88        8 weeks ago         33.3MB
localhost:5000/app-uncompiled   latest              e5f52db674d4        292 years ago       303MB

I don't really know anything about the OCI image spec, but I suspect that there's some missing creation date metadata. It'd be nice if that was accurate.

[jchesterpivotal]

This is almost definitely some sort of underflow. -292 years is approximately -9.2 quintillion nanoseconds and the range of a golang int64 is approximately ± 9.2 quintillion.

[ekcasey]

@nebhale added to the backlog

[nebhale]

Still having the issue:

$: docker images
REPOSITORY                           TAG                 IMAGE ID            CREATED             SIZE
localhost:5000/uncompiled            <none>              72bda8a5c7f0        3 hours ago         310MB
localhost:5000/run                   0.0.1-rc.440        5d79af41489c        3 hours ago         161MB
localhost:5000/run                   v3alpha2            5d79af41489c        3 hours ago         161MB
localhost:5000/uncompiled            <none>              48c0c0614468        3 hours ago         310MB
localhost:5000/build                 v3alpha2            a7f5bfd379bd        3 hours ago         161MB
localhost:5000/builder-open-source   latest              82439e455dc7        3 hours ago         668MB
localhost:5000/builder-commercial    latest              62aa84fb413f        3 hours ago         671MB
localhost:5000/uncompiled            latest              f5ffab0c4789        292 years ago       310MB

Wonder if it has anything to do with the second staging on the same image name?

[mgibson1121]

@sclevine @ekcasey Any particular steps to reproduce this? Not seeing this error on my pack builds when I run docker images using pack ```pack-0.1.0-build.74-darwin`` (however, me not seeing the error in my docker images doesn't mean it's fixed)

[ekcasey]

The error incorrect creation date used to be visible after

1. running a build with --publish
2. pulling the image with docker pull
3. listing images (docker images)

[mgibson1121]

LGTM accepting/