In the past, I had trouble with corrupted log files causing a huge load on the system. Execute for log in /var/lib/docker/containers/*/*-json.log; do jq < $log 2 >&1 /dev/null || echo $log corrupted;done to check if the logfiles are still valid json. Generally make sure /var/lib/docker has plenty of free diskspace.
You question confuses me. How would reading the log files of the docker service or checking for corrupt container logs be related to this?
Though, if you find and delete corrupted logs, you will of course lose the existing log data. If the container is running, it will start writing logs again, but the logs before deleting will be lost for this container.
What is “my docker” for you?
So far I assumed docker as in the docker engine. My answers aimed toward that understanding.
I started to get the feeling that you refer with docker to actual containers… well don’t. a container is not a docker.
You can get the container logs with docker logs {container id or name}. Though, this is so basic knowledge… If this realy is what you asked for, then I strongly suggest to spend some time to actualy learn the basics. I can highly recommend this excellent self paced training.
Hi @krishnananda, from the error you provided in the logs, it seems we are not able to make a successful connection from the container to another service/system. Check out this link to see if that may help you. Also, if you could provide any other details on the configuration of these containers, that will be super helpful in helping you.