When some nodes of k8s run for a period of time, an error is reported: sys/FS/CGroup/memory/docker: no space left on device \ “: unknown
The docker’s memory is full, probably because SELinux = is on
Permanent closure solution:
VI/etc/SELinux/config, change SELinux = enforcing to SELinux = disabled, then save and exit
Then restart the computer
The node can be used after re running
Of course, this is: basic entrance examination of intelligent gtalent operation engineer
If it is only used temporarily, then directly: setenforce 0
docker: Error response from daemon: OCI runtime create failed: container_ linux.go:345: starting container process caused “process_ linux.go:275: applying cgroup configuration for process caused \”mkdir /sys/fs/cgroup/memory/docker: no space left on device\””: unknown.
ERRO[0000] error waiting for container: context canceled
Read More:
- How to Solve kubelet starts error (k8s Cluster Restarted)
- [Solved] Docker startup container error: permission denied””: unknown.
- K8s Install Error: Error: unknown flag: –experimental-upload-certs
- How to Solve mount error(6): No such device or address
- [Solved] k8s kubeadmin init Error: http://localhost:10248/healthz‘ failed
- MAC: How to Solve VirtualBox cannot open Issues
- How to Solve screenfull plug-in Error (Version Issues)
- [Solved] K8s Initialize Error: failed with error: Get “http://localhost:10248/healthz“
- [Solved] Ubuntu 20.04 LTS Install k8s Error: The connection to the server localhost:8080 was refused
- K8S Master Initialize Error: [ERROR CRI]: container runtime is not running: output: E0812
- [Solved] K8s cluster build error: error: kubectl get csr No resources found.
- [Solved] k8s Error: Back-off restarting failed container
- Docker run Error: container_linux.go:235: starting container process caused “process_linux.go:258: appl
- How to Fix ERROR Couldn’t connect to Docker daemon at http+docker://localunixsocket
- How to Solve Docker failed to initialize Error
- How to Solve Git error: out of memory
- Docker: How to Enter the Closed Container and View the Logging
- [Solved] Docker Startup Error: panic: runtime error: invalid memory address or nil pointer dereference
- TensorFlow-gpu Error: failed call to cuInit: CUDA_ERROR_NO_DEVICE: no CUDA-capable device is detected
- How to Solve Docker Error: elasticsearch exception: type=cluster_block_exception, reason=blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];