18juil/19Off
identifier le container docker qui blinde /var/lib/docker
L'installation d'Openshift ne paramètre pas de limite sur le fichier de log docker.
Comment identifier le container docker qui blinde le stockage docker (non persistent).
Contournement:
[root@node003 ~]# df -h /var/lib/docker/
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/docker--vg-dockerlv 500G 419G 82G 84% /var/lib/docker
[root@node003 ~]# find /var/lib/docker -name "*json.log" -size +1G -exec ls -sh {} \;
90G /var/lib/docker/containers/cad8e7540afd8d28fbe7990908cdfa62841b11ea135f956778af9721881cf11c/cad8e7540afd8d28fbe7990908cdfa62841b11ea135f956778af9721881cf11c-json.log
100G /var/lib/docker/containers/7e002100ba95d0478ed6514af30c2c35c1c174f39a48582acdcaeb191c8f866f/7e002100ba95d0478ed6514af30c2c35c1c174f39a48582acdcaeb191c8f866f-json.log
261G /var/lib/docker/containers/17e3f9bb7233220e0ea3b726f760d5666dae0f1fbcbebf59724ce303b4c6925f/17e3f9bb7233220e0ea3b726f760d5666dae0f1fbcbebf59724ce303b4c6925f-json.log
[root@node003 ~]# cat /dev/null > /var/lib/docker/containers/cad8e7540afd8d28fbe7990908cdfa62841b11ea135f956778af9721881cf11c/cad8e7540afd8d28fbe7990908cdfa62841b11ea135f956778af9721881cf11c-json.log
[root@node003 ~]# cat /dev/null > /var/lib/docker/containers/7e002100ba95d0478ed6514af30c2c35c1c174f39a48582acdcaeb191c8f866f/7e002100ba95d0478ed6514af30c2c35c1c174f39a48582acdcaeb191c8f866f-json.log
[root@node003 ~]# cat /dev/null > /var/lib/docker/containers/17e3f9bb7233220e0ea3b726f760d5666dae0f1fbcbebf59724ce303b4c6925f/17e3f9bb7233220e0ea3b726f760d5666dae0f1fbcbebf59724ce303b4c6925f-json.log
[root@node003 ~]# df -h /var/lib/docker/
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/docker--vg-dockerlv 500G 68G 433G 14% /var/lib/docker
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/docker--vg-dockerlv 500G 419G 82G 84% /var/lib/docker
[root@node003 ~]# find /var/lib/docker -name "*json.log" -size +1G -exec ls -sh {} \;
90G /var/lib/docker/containers/cad8e7540afd8d28fbe7990908cdfa62841b11ea135f956778af9721881cf11c/cad8e7540afd8d28fbe7990908cdfa62841b11ea135f956778af9721881cf11c-json.log
100G /var/lib/docker/containers/7e002100ba95d0478ed6514af30c2c35c1c174f39a48582acdcaeb191c8f866f/7e002100ba95d0478ed6514af30c2c35c1c174f39a48582acdcaeb191c8f866f-json.log
261G /var/lib/docker/containers/17e3f9bb7233220e0ea3b726f760d5666dae0f1fbcbebf59724ce303b4c6925f/17e3f9bb7233220e0ea3b726f760d5666dae0f1fbcbebf59724ce303b4c6925f-json.log
[root@node003 ~]# cat /dev/null > /var/lib/docker/containers/cad8e7540afd8d28fbe7990908cdfa62841b11ea135f956778af9721881cf11c/cad8e7540afd8d28fbe7990908cdfa62841b11ea135f956778af9721881cf11c-json.log
[root@node003 ~]# cat /dev/null > /var/lib/docker/containers/7e002100ba95d0478ed6514af30c2c35c1c174f39a48582acdcaeb191c8f866f/7e002100ba95d0478ed6514af30c2c35c1c174f39a48582acdcaeb191c8f866f-json.log
[root@node003 ~]# cat /dev/null > /var/lib/docker/containers/17e3f9bb7233220e0ea3b726f760d5666dae0f1fbcbebf59724ce303b4c6925f/17e3f9bb7233220e0ea3b726f760d5666dae0f1fbcbebf59724ce303b4c6925f-json.log
[root@node003 ~]# df -h /var/lib/docker/
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/docker--vg-dockerlv 500G 68G 433G 14% /var/lib/docker
Résolution:
ajouter l'option --log-opt max-size et --log-opt max-file au fichier de conf /etc/sysconfig/docker
# cat /etc/sysconfig/docker
OPTIONS='--insecure-registry=172.30.0.0/16 --selinux-enabled --log-opt max-size=50m --log-opt max-file=5'
OPTIONS='--insecure-registry=172.30.0.0/16 --selinux-enabled --log-opt max-size=50m --log-opt max-file=5'
Planifier un redémarrage de docker, attention redéploiement des pods
[root@node3003 ~]# systemctl restart docker
Soure: Red HAt