podman with rootless can not execute normal when graphroot device space is full

[lddlww]

Issue Description

when graphroot device space is full, podman like inspect option throw error:

Error: adding container 4711bcb1e4179a8afebf513e340ab08c0fe5595117a02c8e58543eb403dee3c1 exit code 137: unable to open database file: no such file or directory

since sqlite db.sql file is located in graphroot dir ,so sqlite can not write db.sql any more

Steps to reproduce the issue

Steps to reproduce the issue

1. create podman with 100GiB graphroot dir
2. entry graphroot , then exec dd if=/dev/random of=testxx bs=1M count=102400
3. exec podman inspect container_id

Describe the results you received

Error: adding container 4711bcb1e4179a8afebf513e340ab08c0fe5595117a02c8e58543eb403dee3c1 exit code 137: unable to open database file: no such file or directory

Describe the results you expected

podman return successfully without any errors
or does sqlite dir can be customized？

podman info output

host:
  arch: amd64
  buildahVersion: 1.41.4
  cgroupControllers:
  - cpuset
  - cpu
  - io
  - memory
  - pids
  cgroupManager: cgroupfs
  cgroupVersion: v2
  conmon:
    package: conmon_2.1.10+ds1-1build2_amd64
    path: /usr/bin/conmon
    version: 'conmon version 2.1.10, commit: unknown'
  cpuUtilization:
    idlePercent: 99.81
    systemPercent: 0.08
    userPercent: 0.11
  cpus: 144
  databaseBackend: sqlite
  distribution:
    codename: noble
    distribution: ubuntu
    version: "24.04"
  eventLogger: file
  freeLocks: 2047
  hostname: kstack-lxc-node-cn-shenzhen-3-10-58-52-10
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 2003
      size: 1
    - container_id: 1
      host_id: 231072
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 2003
      size: 1
    - container_id: 1
      host_id: 231072
      size: 65536
  kernel: 6.8.0-71-generic
  linkmode: dynamic
  logDriver: k8s-file
  memFree: 94613311488
  memTotal: 1081766395904
  networkBackend: netavark
  networkBackendInfo:
    backend: netavark
    dns:
      package: aardvark-dns_1.4.0-5_amd64
      path: /usr/lib/podman/aardvark-dns
      version: aardvark-dns 1.4.0
    package: netavark_1.4.0-4_amd64
    path: /usr/lib/podman/netavark
    version: netavark 1.4.0
  ociRuntime:
    name: crun
    package: crun_1.14.1-1_amd64
    path: /usr/bin/crun
    version: |-
      crun version 1.22
      commit: 4de19b63a85efd9ea8503452179c371181750130
      rundir: /run/user/2003/crun
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
  os: linux
  pasta:
    executable: /usr/bin/pasta
    package: passt_0.0~git20240220.1e6f92b-1_amd64
    version: |
      pasta unknown version
      Copyright Red Hat
      GNU General Public License, version 2 or later
        <https://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
      This is free software: you are free to change and redistribute it.
      There is NO WARRANTY, to the extent permitted by law.
  remoteSocket:
    exists: true
    path: /run/user/2003/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: false
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns_1.2.1-1build2_amd64
    version: |-
      slirp4netns version 1.2.1
      commit: 09e31e92fa3d2a1d3ca261adaeb012c8d75a8194
      libslirp: 4.7.0
      SLIRP_CONFIG_VERSION_MAX: 4
      libseccomp: 2.5.5
  swapFree: 8586739712
  swapTotal: 8589930496
  uptime: 481h 11m 55.00s (Approximately 20.04 days)
  variant: ""
plugins:
  authorization: null
  log:
  - k8s-file
  - none
  - passthrough
  network:
  - bridge
  - macvlan
  - ipvlan
  volume:
  - local
registries: {}
store:
  configFile: /opt/containers/group/b845b2ce/.config/containers/storage.conf
  containerStore:
    number: 1
    paused: 0
    running: 1
    stopped: 0
  graphDriverName: overlay
  graphOptions:
    overlay.additionalImageStores:
    - /opt/containers/pub_img
    overlay.imagestore: /opt/containers/pub_img
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: fuse-overlayfs_1.13-1_amd64
      Version: |-
        fusermount3 version: 3.14.0
        fuse-overlayfs: version 1.13-dev
        FUSE library version 3.14.0
        using FUSE kernel interface version 7.31
  graphRoot: /opt/containers/group/b845b2ce/b845b2ce-root
  graphRootAllocated: 107307073536
  graphRootUsed: 2093932544
  graphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Supports shifting: "true"
    Supports volatile: "true"
    Using metacopy: "false"
  imageCopyTmpDir: /var/tmp
  imageStore:
    number: 25
  runRoot: /run/user/2003/containers
  transientStore: false
  volumePath: /opt/containers/group/b845b2ce/b845b2ce-root/volumes
version:
  APIVersion: 5.6.1
  Built: 1757932221
  BuiltTime: Mon Sep 15 18:30:21 2025
  GitCommit: ""
  GoVersion: go1.24.6
  Os: linux
  OsArch: linux/amd64
  Version: 5.6.1

Podman in a container

No

Privileged Or Rootless

None

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

[mheon]

Dupe of #13967 but it's gotten worse since we looked last - SQLite can't even open the database without open space, so we fail even earlier. I think the discussions of what to do still apply as well - allocate some storage we can delete when necessary to allow the DB to open?

@baude @Luap99 PTAL

[Luap99]

I don't think it is different, the error isn't early

adding container 4711bcb1e4179a8afebf513e340ab08c0fe5595117a02c8e58543eb403dee3c1 exit code 137: ...

That is the error message from AddContainerExitCode() so it has to do an write here so it just seems logical of sqlite to fail here, though no idea why it would report it has no such file or directory instead of no space.

In any case lets keep the conversation in the original report.