21.4. Podman 시스템 정보 표시

사전 요구 사항

• container-tools meta-package가 설치되어 있습니다.

절차

• Podman 시스템 정보를 표시합니다.

  • Podman 디스크 사용량을 표시하려면 다음을 입력합니다.

    $ podman system df
    TYPE           TOTAL       ACTIVE      SIZE        RECLAIMABLE
    Images         3           2           1.085GB     233.4MB (0%)
    Containers     2           0           28.17kB     28.17kB (100%)
    Local Volumes  3           0           0B          0B (0%)

  • 공간 사용량에 대한 자세한 정보를 표시하려면 다음을 입력합니다.

    $ podman system df -v
    Images space usage:
    
    REPOSITORY                                TAG         IMAGE ID      CREATED     SIZE        SHARED SIZE  UNIQUE SIZE  CONTAINERS
    registry.access.redhat.com/ubi9           latest      b1e63aaae5cf  13 days     233.4MB     233.4MB      0B           0
    registry.access.redhat.com/ubi9/httpd-24  latest      0d04740850e8  13 days     461.5MB     0B           461.5MB      1
    registry.redhat.io/rhel8/podman           latest      dce10f591a2d  13 days     390.6MB     233.4MB      157.2MB      1
    
    Containers space usage:
    
    CONTAINER ID  IMAGE         COMMAND                     LOCAL VOLUMES  SIZE        CREATED     STATUS      NAMES
    311180ab99fb  0d04740850e8  /usr/bin/run-httpd          0              28.17kB     16 hours    exited      hc1
    bedb6c287ed6  dce10f591a2d  podman run ubi9 echo hello  0              0B          11 hours    configured  dazzling_tu
    
    Local Volumes space usage:
    
    VOLUME NAME                                                       LINKS       SIZE
    76de0efa83a3dae1a388b9e9e67161d28187e093955df185ea228ad0b3e435d0  0           0B
    8a1b4658aecc9ff38711a2c7f2da6de192c5b1e753bb7e3b25e9bf3bb7da8b13  0           0B
    d9cab4f6ccbcf2ac3cd750d2efff9d2b0f29411d430a119210dd242e8be20e26  0           0B

  • 호스트에 대한 정보, 현재 스토리지 통계 및 Podman 빌드를 표시하려면 다음을 입력합니다.

    $ podman system info
    host:
      arch: amd64
      buildahVersion: 1.22.3
      cgroupControllers: []
      cgroupManager: cgroupfs
      cgroupVersion: v1
      conmon:
        package: conmon-2.0.29-1.module+el8.5.0+12381+e822eb26.x86_64
        path: /usr/bin/conmon
        version: 'conmon version 2.0.29, commit: 7d0fa63455025991c2fc641da85922fde889c91b'
      cpus: 2
      distribution:
        distribution: '"rhel"'
        version: "8.5"
      eventLogger: file
      hostname: localhost.localdomain
      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: 4.18.0-323.el8.x86_64
      linkmode: dynamic
      memFree: 352288768
      memTotal: 2819129344
      ociRuntime:
        name: runc
        package: runc-1.0.2-1.module+el8.5.0+12381+e822eb26.x86_64
        path: /usr/bin/runc
        version: |-
          runc version 1.0.2
          spec: 1.0.2-dev
          go: go1.16.7
          libseccomp: 2.5.1
      os: linux
      remoteSocket:
        path: /run/user/1000/podman/podman.sock
      security:
        apparmorEnabled: false
        capabilities: CAP_NET_RAW,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.1.8-1.module+el8.5.0+12381+e822eb26.x86_64
        version: |-
          slirp4netns version 1.1.8
          commit: d361001f495417b880f20329121e3aa431a8f90f
          libslirp: 4.4.0
          SLIRP_CONFIG_VERSION_MAX: 3
          libseccomp: 2.5.1
      swapFree: 3113668608
      swapTotal: 3124752384
      uptime: 11h 24m 12.52s (Approximately 0.46 days)
    registries:
      search:
      - registry.fedoraproject.org
      - registry.access.redhat.com
      - registry.centos.org
      - docker.io
    store:
      configFile: /home/user/.config/containers/storage.conf
      containerStore:
        number: 2
        paused: 0
        running: 0
        stopped: 2
      graphDriverName: overlay
      graphOptions:
        overlay.mount_program:
          Executable: /usr/bin/fuse-overlayfs
          Package: fuse-overlayfs-1.7.1-1.module+el8.5.0+12381+e822eb26.x86_64
          Version: |-
            fusermount3 version: 3.2.1
            fuse-overlayfs: version 1.7.1
            FUSE library version 3.2.1
            using FUSE kernel interface version 7.26
      graphRoot: /home/user/.local/share/containers/storage
      graphStatus:
        Backing Filesystem: xfs
        Native Overlay Diff: "false"
        Supports d_type: "true"
        Using metacopy: "false"
      imageStore:
        number: 3
      runRoot: /run/user/1000/containers
      volumePath: /home/user/.local/share/containers/storage/volumes
    version:
      APIVersion: 3.3.1
      Built: 1630360721
      BuiltTime: Mon Aug 30 23:58:41 2021
      GitCommit: ""
      GoVersion: go1.16.7
      OsArch: linux/amd64
      Version: 3.3.1

  • 사용되지 않는 모든 컨테이너, 이미지 및 볼륨 데이터를 제거하려면 다음을 입력합니다.

    $ podman system prune
    WARNING! This will remove:
            - all stopped containers
            - all stopped pods
            - all dangling images
            - all build cache
    Are you sure you want to continue? [y/N] y

    • podman system prune 명령은 사용되지 않는 모든 컨테이너(대각 및 역참조), Pod 및 선택적으로 로컬 스토리지에서 볼륨을 제거합니다.
    • 사용하지 않는 이미지를 모두 삭제하려면 --all 옵션을 사용합니다. 사용되지 않는 이미지는 이미지 및 컨테이너 기반의 컨테이너가 없는 이미지입니다.
    • --volume 옵션을 사용하여 볼륨을 정리합니다. 현재 볼륨을 사용하는 컨테이너가 없는 경우 중요한 데이터가 삭제되지 않도록 볼륨이 기본적으로 제거되지 않습니다.