Disk quota exceeded error

[lystormenvoy]

After running a period of time. All my containers stopped (STATUS in podman ps). But the conmon processes still runing(?). I can see conmon processes in ps -ef | grep conmon.
When I try to podman start containername.
It print:
Error: OCI runtime error: unable to start container "xxxxx": crun : create keyring 'xxx': Disk quota exceeded

When I run quota -uvs myuser there is no print.

crun -V

crun version 1.4.5
commit: c381048530aa750495cf502ddb7181f2ded5b400
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL

It work after reboot the system.

[rhatdan]

Docker does not use conmon? Or are you using podman with an alias to docker? Or docker client talking to podman service?

[giuseppe]

why do you think it is an issue in crun?

[lystormenvoy]

Docker does not use conmon? Or are you using podman with an alias to docker? Or docker client talking to podman service?

Sorry, I use podman with an alias to docker.

[lystormenvoy]

why do you think it is an issue in crun?

The print seems that the crun can't start because some quota limit, when the system has no quota setting.

[rhatdan]

This error is returned in
libcrun_create_keyring (const char *name, const char *label, libcrun_error_t *err)

In crun.

Could you try using runc to see if same error happens.

What OS and What kernel are you using? Could this be a kernel compiled with strange or no kernel keyring support.

[lystormenvoy]

My kernel:
Linux g2-alive-hz-03 4.18.0-372.9.1.an8.x86_64 #1 SMP Mon May 16 20:40:40 CST 2022 x86_64 x86_64 x86_64 GNU/Linux

It happened just one time. It has run for two days without error.

[giuseppe]

it could be a legit error. Maybe too many keyrings were already created

[lystormenvoy]

Maybe, I am waiting for reproducing.

[giuseppe]

any update on this issue?

[giuseppe]

we haven't got any update, so I am closing the issue

Please reopen if you've more data to share