Podman stats does not show memory limits set per container (aarch64)

[alosadagrande]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

Wanted to limit the memory used by a container, however the memory limit it is not visualized in the stats command.

Podman is running on a F33 on a raspberry pi3 (aarch64)

Steps to reproduce the issue:

1. Run a container limiting the memory to use:

# podman run -d --rm --memory=64m busybox sleep 1000000000000000
ff622b233d98cc083529ba01e9f937e9483eebfc1ad52ffef35cbecde4b1ee93

2. Verify the stats

# podman stats

ID            NAME            CPU %   MEM USAGE / LIMIT  MEM %   NET IO          BLOCK IO           PIDS
7ccb9e39ee32  home-assistant  7.91%   219.3MB / 981.1MB  22.35%  -- / --         276.8MB / 39.99MB  92
ff622b233d98  angry_edison    --      1.069MB / 981.1MB  0.11%   628B / 1.646kB  757.8kB / 0B       1

Describe the results you received:

Podman stats shows the limit of the container to be the total amount of memory of the rpi3.

Describe the results you expected:

I would expect to see the limit set explicitly for the container. Basically, the same it shows in my laptop (Fedora x86_64)

Additional information you deem important (e.g. issue happens only occasionally):

This issue seems to show only in my ARM server.

Output of podman version:

# podman --version
podman version 2.1.1

Output of podman info --debug:

# podman info --debug
host:
  arch: arm64
  buildahVersion: 1.16.1
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon-2.0.21-3.fc33.aarch64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.21, commit: 66d50d2f6c81e28bacd99ee8e8d222f028eef63f'
  cpus: 4
  distribution:
    distribution: fedora
    version: "33"
  eventLogger: journald
  idMappings:
    gidmap: null
    uidmap: null
  kernel: 5.8.18-300.fc33.aarch64
  linkmode: dynamic
  memFree: 189890560
  memTotal: 981086208
  ociRuntime:
    name: crun
    package: crun-0.15-5.fc33.aarch64
    path: /usr/bin/crun
    version: |-
      crun version 0.15
      commit: 56ca95e61639510c7dbd39ff512f80f626404969
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
  os: linux
  remoteSocket:
    path: /run/podman/podman.sock
  rootless: false
  slirp4netns:
    executable: ""
    package: ""
    version: ""
  swapFree: 373813248
  swapTotal: 489680896
  uptime: 1h 32m 12.61s (Approximately 0.04 days)
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - registry.centos.org
  - docker.io
store:
  configFile: /etc/containers/storage.conf
  containerStore:
    number: 2
    paused: 0
    running: 2
    stopped: 0
  graphDriverName: overlay
  graphOptions:
    overlay.mountopt: nodev,metacopy=on
  graphRoot: /var/lib/containers/storage
  graphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "true"
  imageStore:
    number: 4
  runRoot: /var/run/containers/storage
  volumePath: /var/lib/containers/storage/volumes
version:
  APIVersion: 2.0.0
  Built: 1602087702
  BuiltTime: Wed Oct  7 18:21:42 2020
  GitCommit: ""
  GoVersion: go1.15.2
  OsArch: linux/arm64
  Version: 2.1.1

Package info (e.g. output of rpm -q podman or apt list podman):

podman-2.1.1-12.fc33.aarch64

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?

Yes

Additional environment details (AWS, VirtualBox, physical, etc.):

physical ARM arch. Same behaviour in FC32 aarch

[mheon]

@vrothberg PTAL

[vrothberg]

I don't think that's a good first issue as it's a bug in the cgroups package, not a simple front end one.