Syx

> @xuegege5290 you're right. We require a runtime glibc because of some cgo related dependencies. Alternatively we could build using musl libc, but that's something we decided against a few...

> Usually the scope has succeeded if there are no more processes left it in. So that `sleep 3600s` process that is in your listing under "normal circumstances" (or whatever...

> > However, I am puzzled because the container remains in a running state and I can still execute the exec command. > > Does `runc` tells you the container...

I found a similar issue discussed in the forum: https://github.com/opencontainers/runc/discussions/4153 https://github.com/opencontainers/runc/commit/39914db679b008d7400a165b974f5d7ceec19e1f

> > > > However, I am puzzled because the container remains in a running state and I can still execute the exec command. > > > > > >...

> > > > However, I am puzzled because the container remains in a running state and I can still execute the exec command. > > > > > >...

Do you need any additional information? ```bash [root@oss38 ~]# systemctl status crio-conmon-32da98c8522068be05a7510a3eddb09cad6ed2f03286180d0e931d0d0b6224a6.scope ● crio-conmon-32da98c8522068be05a7510a3eddb09cad6ed2f03286180d0e931d0d0b6224a6.scope Loaded: loaded (/run/systemd/transient/crio-conmon-32da98c8522068be05a7510a3eddb09cad6ed2f03286180d0e931d0d0b6224a6.scope; transient) Transient: yes Active: active (running) since Tue 2025-02-11 15:37:50 CST; 51min ago...

Partial logs ```bash Feb 11 15:37:50 oss38 systemd[1]: Started crio-conmon-32da98c8522068be05a7510a3eddb09cad6ed2f03286180d0e931d0d0b6224a6.scope. Feb 11 15:37:50 oss38 conmon[21942]: conmon 32da98c8522068be05a7 : addr{sun_family=AF_UNIX, sun_path=/proc/self/fd/12/attach} Feb 11 15:37:50 oss38 conmon[21942]: conmon 32da98c8522068be05a7 : terminal_ctrl_fd: 12...

Another container ```bash [root@oss38 ~]# runc --root /run/runc list |grep 28a39c6a840cc 28a39c6a840cc5f388ac395aea5f969f91074aea718fd983b2475eb7a1e8fe4a 23438 running /run/containers/storage/overlay-containers/28a39c6a840cc5f388ac395aea5f969f91074aea718fd983b2475eb7a1e8fe4a/userdata 2025-02-11T07:37:53.728810543Z root [root@oss38 ~]# runc --root /run/runc exec -t 28a39c6a840cc5f388ac395aea5f969f91074aea718fd983b2475eb7a1e8fe4a date ERRO[0000] exec failed: unable...

> Could you please help to provide more informations, for example: > > 1. The content of `config.json`; > 2. `ls /sys/fs/cgroup/systemd/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pod207aaad1_659f_4db8_88e0_46e0cdcc3004.slice/crio-32da98c8522068be05a7510a3eddb09cad6ed2f03286180d0e931d0d0b6224a6.scope`; > 3. `cat /sys/fs/cgroup/systemd/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pod207aaad1_659f_4db8_88e0_46e0cdcc3004.slice/crio-32da98c8522068be05a7510a3eddb09cad6ed2f03286180d0e931d0d0b6224a6.scope/cgroup.procs`; > > And I...