1. Error reporting:
Use the journalctl – xefu kubelet command to view the kubelet log. The following errors are found:
cannot find network namespace for the terminated container
2. Solution:
# docker system prune
# systemctl restart kubelet
Instructions for using docker system:
# docker system -h
Flag shorthand -h has been deprecated, please use –help
Usage: docker system COMMAND
Manage Docker
Commands:
df Show docker disk usage
Check the usage of docker space.
events Get real time events from the server
View live events.
info Display system-wide information
View system information.
prune Remove unused data
Docker cleans the stopped container, and there is no network, image and cache used by the container.
Read More:
- Docker creation container cannot find network card: error response from daemon: network XXXX not found
- [Solved] “Failed to run kubelet“ err=“failed to run Kubelet: misconfiguration: kubelet cgroup driver: \“cgrou
- error starting container: API error (404): network fabric_test not found“
- [Solved] Fabric 2.x: error starting container: API error (404): network_test not found
- [Solved] Docker startup container error: permission denied””: unknown.
- Node Kubelet Error: node “xxxxx“ not found [How to Solve]
- error CS0234: The type or namespace name ‘UI‘ does not exist in the namespace ‘UnityEngine‘
- How to Solve kubelet starts error (k8s Cluster Restarted)
- Wireless network solution of deepin Linux network card driver (manual) installation
- Error running docker container: starting container process caused “exec: \“python\“: executable file
- Error from server (alreadyexists) clusterrolebindings.rbac.authorization .k8s.io “kubelet
- Debian using networking to restart the network can not start the solution of network card
- When docker starts tomcat, the access port of the container displays 404, and the source server fails to find the representation of the target resource or is unwilling to disclose an existing one
- [Solved] CCS compilation and debug error: Source lookup: unable to restore CPU specific source container – expecting valid source container id value.
- Docker run Error: container_linux.go:235: starting container process caused “process_linux.go:258: appl
- Get connection timeout retry: 1 MySQL errorcode 0, state 08s01 docker container accessing MySQL container is very slow and sometimes interrupted
- Linux virtual machine network “job for” network.service failed because the control process exited with error code”
- Solution summary of VMware network card without IP and failure to start network card (continuous update)
- [Solved] dyld: Library not loaded: /System/Library/Frameworks/Network.framework/Network
- [Solved] Windows startup error: unable to find launcherrsxruntime.exe