Closed taqtiqa-mark closed 7 years ago
Now I am guessing. But in case it helps save someone else N build runs.... if acbuild is using a std go library, this page, hints that these might be allowed timestamps. True? who knows.
ANSIC = "Mon Jan _2 15:04:05 2006"
UnixDate = "Mon Jan _2 15:04:05 MST 2006"
RubyDate = "Mon Jan 02 15:04:05 -0700 2006"
RFC822 = "02 Jan 06 15:04 MST"
RFC822Z = "02 Jan 06 15:04 -0700" // RFC822 with numeric zone
RFC850 = "Monday, 02-Jan-06 15:04:05 MST"
RFC1123 = "Mon, 02 Jan 2006 15:04:05 MST"
RFC1123Z = "Mon, 02 Jan 2006 15:04:05 -0700" // RFC1123 with numeric zone
RFC3339 = "2006-01-02T15:04:05Z07:00"
RFC3339Nano = "2006-01-02T15:04:05.999999999Z07:00"
Kitchen = "3:04PM"
// Handy time stamps.
Stamp = "Jan _2 15:04:05"
StampMilli = "Jan _2 15:04:05.000"
StampMicro = "Jan _2 15:04:05.000000"
StampNano = "Jan _2 15:04:05.000000000"
No need to guess, the type of that field is fully specified here: https://github.com/appc/spec/blob/master/spec/types.md#timestamps-type, even with an example on how to produce it. From your list above, this corresponds to RFC3339Nano
.
I'm closing this. The project is no longer maintained and umoci and buildah are likely the tools people should be looking at. With that as context, this issue is just noise.
This build step
results in this error
The documentation here is silent
Hope this helps.