-
Observed Kubernetes workload deployment failure caused by excessive logging in /run/containerd/io.containerd.runtime.v2.task/k8s.io//log.json file. This leads to /run tmpfs mount to be at 100% utiliz…
-
### What is the problem you're trying to solve
Looking in pkg/ocihook, we don't seem to have to have any tests to ensure these OCI hooks are working as intended. We have one test in [container_run_te…
-
I would like to run RunC containers based on nvidia-docker rootless. But using the runtime hook I get
```
container_linux.go:348: starting container process caused "process_linux.go:402: containe…
-
### Description
poststart run into runc create stage. doesn't match the runtime-spec
the spec say "poststart after the user-specified process is executed but before the start operation returns"
…
-
## Feature Request
**Short Description**
Use OCI hooks and get events in context to container start/stop: Currently KubeArmor mounts docker/containerd/crio UNIX domain socket file in KubeArmor …
-
Hello,
oci-systemd-hook on latest RHEL atomic host doesn't work with runc.
```
# atomic host status
State: idle
Deployments:
● rhel-atomic-host:rhel-atomic-host/7/x86_64/standard
…
-
I am not sure what is going on here
`Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start cont…
-
![微信截图_20240207162150](https://github.com/netease-youdao/QAnything/assets/62528328/55fcf9b5-691e-4cec-baf0-eddd28178b2d)
Error response from daemon: failed to create task for container: failed to cre…
-
_The template below is mostly useful for bug reports and support questions. Feel free to remove anything which doesn't apply to you and add more information where it makes sense._
---
### 1. Issue…
-
We have tried to create a new docker container starting by using the docker image that is using on the vLLM example given in this repo and we got the below error:
Errors occurred while bootstrappin…