The container´s volumes apprears as a mounted filesystems. in the OS space:
Filesystem Size Used Avail Use% Mounted on overlay 197G 2.4G 185G 2% /docker/overlay2/9ed21fb91438df2b5b59212878d74b2c4054fd771aa6004cfadee912371d13a3/merged overlay 197G 2.4G 185G 2% /docker/overlay2/7359de2d4d7e19fb75daa34d51d21db1c02a44c99ac30aafca840c8ab4df5b5c/merged overlay 197G 2.4G 185G 2% /docker/overlay2/38086a3800656e9f92dfc24857c009d5b5ee1c22ad580edba4293ca0d9feacb6/merged
Every time the container restarts, it´s volumes will change the hash name. This is an expected behavior. Somehow, SCOM can´t handle this and assumes that the old disk is not there anymore (That is technically true) and triggers an alarm and an incident is created automatically. We need to find a way to stop this false positives as they are losing their purpose. By getting so many of them, we might lose a real alert in a sea of false positives. Any comments ?
-py