| eG Monitoring |
|---|
|
Measures reported by DockInfoTest When the Docker service runs for the first time in the Docker server, a defined quantity of data space and metadata space is allocated from the Docker volume, using which data can be stored in the Docker container outside of the boot volume (but within the root file system). By default, the Docker offers thin provisioning facility of volumes which means that you have a big pool of available storage blocks within the volume and can create block devices such as virtual disks, of arbitrary size from that pool. The storage blocks will be marked as used or taken from the pool only when you actually write to it. The storage blocks are mapped to the data space and the metadata space for storage needs. Here, the Docker images are stored in the data space and the definite data about the docker images are stored in the metadata space. Since the Docker images are the basic building blocks of the Docker, if the data space or the metadata space is not sufficient, then new images and new containers based on the images cannot be created. If sufficient images are not available, then users cannot create new containers and simultaneously applications will also become inaccessible or the users will have only a limited choice of applications. To avoid such eventualities, it is inevitable that the data space and metadata space be monitored at regular intervals. The DockInfoTest test helps you in this regard! This test reports the utilization of data and metadata space within a Docker server and proactively alerts administrators to potential space crunch, if any. Note: This test will run only if the Docker server is installed with the Device Mapper, which is a Linux kernel's framework for mapping physical block devices onto higher-level virtual block devices. Outputs of the test : One set of results for the Docker server being monitored The measures made by this test are as follows:
|