Description
This issue was opened on Moby by @brimworks but since it's related to this repository I am opening it here.
Output of docker history --human=false changed which breaks anyone relying on the expected ISO8601 time format.
Steps to reproduce the issue:
- Pull an image, for example: docker pull alpine
- Run docker history with the --human=false flag as documented here:
https://docs.docker.com/engine/reference/commandline/history/#description
For example:
docker history -H=false --format='{{ json . }}' alpine | jq
{
"Comment": "",
"CreatedAt": "6 weeks",
"CreatedBy": "/bin/sh -c #(nop) CMD [\"/bin/sh\"]",
"CreatedSince": "6 weeks ago",
"ID": "7328f6f8b418",
"Size": "0"
}
{
"Comment": "",
"CreatedAt": "6 weeks",
"CreatedBy": "/bin/sh -c #(nop) ADD file:4583e12bf5caec4...",
"CreatedSince": "6 weeks ago",
"ID": "<missing>",
"Size": "3965955"
}
Describe the results you received:
The CreatedSince fields was a "human readable" relative time.
Describe the results you expected:
Expected CreatedSince to be in ISO8601 time format.
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
Client:
Version: unknown-version
API version: 1.30
Go version: go1.8.3
Git commit: unknown-commit
Built: unknown-buildtime
OS/Arch: linux/amd64
Server:
Version: 17.06.0-dev
API version: 1.32 (minimum version 1.12)
Go version: go1.8.3
Git commit: 2638729c7
Built: Thu Aug 10 21:43:50 2017
OS/Arch: linux/amd64
Experimental: false
Output of docker info:
Containers: 0 [18/4820]
Running: 0
Paused: 0
Stopped: 0
Images: 1
Server Version: 17.06.0-dev
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 3addd840653146c90a254301d6c3a663c7fd6429
runc version: 2d41c047c83e09a6d61d464906feb2a2f3c52aa4
init version: 949e6fa
Security Options:
seccomp
Profile: default
Kernel Version: 4.11.11-300.fc26.x86_64
Operating System: Debian GNU/Linux 8 (jessie) (containerized)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 11.43GiB
Name: f64fd39afcbd
ID: YPSQ:SSTB:THER:4PGG:IIAW:XJJL:6BYP:3Q37:SENJ:Q3L3:2GZV:2RSV
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 20
Goroutines: 31
System Time: 2017-08-12T18:20:05.949159727Z
EventsListeners: 1
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
Additional environment details (AWS, VirtualBox, physical, etc.):
physical
Description
This issue was opened on Moby by @brimworks but since it's related to this repository I am opening it here.
Output of
docker history --human=falsechanged which breaks anyone relying on the expectedISO8601time format.Steps to reproduce the issue:
https://docs.docker.com/engine/reference/commandline/history/#description
For example:
Describe the results you received:
The CreatedSince fields was a "human readable" relative time.
Describe the results you expected:
Expected CreatedSince to be in
ISO8601time format.Additional information you deem important (e.g. issue happens only occasionally):
Output of
docker version:Output of
docker info:Additional environment details (AWS, VirtualBox, physical, etc.):
physical