Description
I would like to express my concern for the health of whoever decided to remove timestamp from the docker images printout. They might have brain damage that even they are not aware of. This change is so extraordinarily backwards, I cannot imagine that a healthy mind would come up with this idea.
I have to admit though, I laughed out loud when I realized, to add it back I have to pass a json to --format string. I think this has to be the most human-unfriendly design I have ever witnessed.
Best regards, and a healthy recovery
Reproduce
docker images
Expected behavior
smart
docker version
Client: Docker Engine - Community
Version: 29.4.0
API version: 1.54
Go version: go1.26.1
Git commit: 9d7ad9f
Built: Tue Apr 7 08:35:18 2026
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 29.4.0
API version: 1.54 (minimum version 1.40)
Go version: go1.26.1
Git commit: daa0cb7
Built: Tue Apr 7 08:35:18 2026
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v2.2.2
GitCommit: 301b2dac98f15c27117da5c8af12118a041a31d9
runc:
Version: 1.3.4
GitCommit: v1.3.4-0-gd6d73eb8
docker-init:
Version: 0.19.0
GitCommit: de40ad0
docker info
Client: Docker Engine - Community
Version: 29.4.0
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.33.0
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v5.1.2
Path: /usr/libexec/docker/cli-plugins/docker-compose
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 311
Server Version: 29.4.0
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
CDI spec directories:
/etc/cdi
/var/run/cdi
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 301b2dac98f15c27117da5c8af12118a041a31d9
runc version: v1.3.4-0-gd6d73eb8
init version: de40ad0
Security Options:
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.18.33.2-microsoft-standard-WSL2
Operating System: Ubuntu 22.04.5 LTS
OSType: linux
Architecture: x86_64
CPUs: 6
Total Memory: 23.47GiB
Name: E-5CG20903L1
ID: 02abad94-f7cd-4563-a7ba-6e111daf7bdc
Docker Root Dir: /var/lib/docker
Debug Mode: false
Experimental: false
Insecure Registries:
::1/128
127.0.0.0/8
Live Restore Enabled: false
Firewall Backend: iptablesAdditional Info
No response
Description
I would like to express my concern for the health of whoever decided to remove timestamp from the docker images printout. They might have brain damage that even they are not aware of. This change is so extraordinarily backwards, I cannot imagine that a healthy mind would come up with this idea.
I have to admit though, I laughed out loud when I realized, to add it back I have to pass a json to --format string. I think this has to be the most human-unfriendly design I have ever witnessed.
Best regards, and a healthy recovery
Reproduce
docker images
Expected behavior
smart
docker version
Client: Docker Engine - Community Version: 29.4.0 API version: 1.54 Go version: go1.26.1 Git commit: 9d7ad9f Built: Tue Apr 7 08:35:18 2026 OS/Arch: linux/amd64 Context: default Server: Docker Engine - Community Engine: Version: 29.4.0 API version: 1.54 (minimum version 1.40) Go version: go1.26.1 Git commit: daa0cb7 Built: Tue Apr 7 08:35:18 2026 OS/Arch: linux/amd64 Experimental: false containerd: Version: v2.2.2 GitCommit: 301b2dac98f15c27117da5c8af12118a041a31d9 runc: Version: 1.3.4 GitCommit: v1.3.4-0-gd6d73eb8 docker-init: Version: 0.19.0 GitCommit: de40ad0docker info
Additional Info
No response