Incorrect duration status in podman ps #26192
Comments
|
Is it possible that your system clock is/was wrong and then later adjusted after the container was started? Podman stores timestamps and then if you change the system time any such calculations will be wrong. |
It's possible as I didn't explicitly check the date/time at system boot, but I do run tmux which has a date/clock in it's status bar and it's always been correct. After rebooting the raspberry pi today |
|
I think that is the most likely explanation. So overall I see no good way to fix this, I suppose for uptime of the container we could generate the duration on the server and adding this as new API field but given it cannot be used for the created time that seems like unnecessary complexity. There is also #23022 which shows that even some internals of podman depend on the time which is obviously not good. |
Issue Description
Hi all, when I run
podman psit shows an incorrect uptime under 'status'. For example it's showing 'Up 2 months' but the system has only been running for 16 hours and this entire system was only installed 1 month ago with a clean install.I'm running this all on Almalinux 9 on a Raspberry pi 5 8bg
Steps to reproduce the issue
Steps to reproduce the issue
podman psDescribe the results you received
Incorrect uptime
Describe the results you expected
Correct uptime
podman info output
host: arch: arm64 buildahVersion: 1.39.4 cgroupControllers: - pids cgroupManager: systemd cgroupVersion: v2 conmon: package: conmon-2.1.12-1.el9.aarch64 path: /usr/bin/conmon version: 'conmon version 2.1.12, commit: 14d5d44d7845e0ec00e607c1a80a2c6b9b33784e' cpuUtilization: idlePercent: 99.53 systemPercent: 0.3 userPercent: 0.16 cpus: 4 databaseBackend: sqlite distribution: distribution: almalinux version: "9.6" eventLogger: journald freeLocks: 2027 hostname: hostname.local idMappings: gidmap: - container_id: 0 host_id: 1000 size: 1 - container_id: 1 host_id: 100000 size: 65536 uidmap: - container_id: 0 host_id: 1000 size: 1 - container_id: 1 host_id: 100000 size: 65536 kernel: 6.6.74-20250127.v8.1.el9 linkmode: dynamic logDriver: journald memFree: 4321705984 memTotal: 8331169792 networkBackend: netavark networkBackendInfo: backend: netavark dns: package: aardvark-dns-1.14.0-1.el9.aarch64 path: /usr/libexec/podman/aardvark-dns version: aardvark-dns 1.14.0 package: netavark-1.14.1-1.el9_6.aarch64 path: /usr/libexec/podman/netavark version: netavark 1.14.1 ociRuntime: name: crun package: crun-1.21-1.el9_6.aarch64 path: /usr/bin/crun version: |- crun version 1.21 commit: 10269840aa07fb7e6b7e1acff6198692d8ff5c88 rundir: /run/user/1000/crun spec: 1.0.0 +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL os: linux pasta: executable: /usr/bin/pasta package: passt-0^20250217.ga1e48a0-1.el9.aarch64 version: "" remoteSocket: exists: true path: /run/user/1000/podman/podman.sock rootlessNetworkCmd: pasta security: apparmorEnabled: false capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT rootless: true seccompEnabled: true seccompProfilePath: /usr/share/containers/seccomp.json selinuxEnabled: true serviceIsRemote: false slirp4netns: executable: /usr/bin/slirp4netns package: slirp4netns-1.3.2-1.el9.aarch64 version: |- slirp4netns version 1.3.2 commit: 0f13345bcef588d2bb70d662d41e92ee8a816d85 libslirp: 4.4.0 SLIRP_CONFIG_VERSION_MAX: 3 libseccomp: 2.5.2 swapFree: 4294963200 swapTotal: 4294963200 uptime: 20h 6m 19.00s (Approximately 0.83 days) variant: v8 plugins: authorization: null log: - k8s-file - none - passthrough - journald network: - bridge - macvlan - ipvlan volume: - local registries: search: - registry.access.redhat.com - registry.redhat.io - docker.io store: configFile: /home/user/.config/containers/storage.conf containerStore: number: 8 paused: 0 running: 7 stopped: 1 graphDriverName: overlay graphOptions: {} graphRoot: /home/user/.local/share/containers/storage graphRootAllocated: 235732176896 graphRootUsed: 88643289088 graphStatus: Backing Filesystem: extfs Native Overlay Diff: "true" Supports d_type: "true" Supports shifting: "false" Supports volatile: "true" Using metacopy: "false" imageCopyTmpDir: /var/tmp imageStore: number: 15 plugins: authorization: null log: - k8s-file - none - passthrough - journald network: - bridge - macvlan - ipvlan volume: - local registries: search: - registry.access.redhat.com - registry.redhat.io - docker.io store: configFile: /home/user/.config/containers/storage.conf containerStore: number: 8 paused: 0 running: 7 stopped: 1 graphDriverName: overlay graphOptions: {} graphRoot: /home/user/.local/share/containers/storage graphRootAllocated: 235732176896 graphRootUsed: 88643289088 graphStatus: Backing Filesystem: extfs Native Overlay Diff: "true" Supports d_type: "true" Supports shifting: "false" Supports volatile: "true" Using metacopy: "false" imageCopyTmpDir: /var/tmp imageStore: number: 15Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: