[Podman] Re: flooded with - Couldn't stat device /dev/char/10:200: No such file or directory

Hi guys. I'd like to ask around about some error messages journal gets full of, namely: ... SELinux: mount invalid.  Same superblock, different security settings for (dev mqueue, type mqueue) Couldn't stat device /dev/char/10:200: No such file or directory Couldn't stat device /dev/char/10:200: No such file or directory Started libcontainer container 391b1013c06ea5abe461d9474ec3b8f2c8e902e9d4b0e0cbf5ea8b8b0394541f. SELinux: mount invalid.  Same superblock, different security settings for (dev mqueue, type mqueue) Couldn't stat device /dev/char/10:200: No such file or directory libpod-238a14cc41bdb2826850c00907c249e43b0b3333c0a344f99920adddff5c38e3.scope: Succeeded. libpod-238a14cc41bdb2826850c00907c249e43b0b3333c0a344f99920adddff5c38e3.scope: Consumed 168ms CPU time libpod-391b1013c06ea5abe461d9474ec3b8f2c8e902e9d4b0e0cbf5ea8b8b0394541f.scope: Succeeded. libpod-391b1013c06ea5abe461d9474ec3b8f2c8e902e9d4b0e0cbf5ea8b8b0394541f.scope: Consumed 150ms CPU time Couldn't stat device /dev/char/10:200: No such file or directory Started libcontainer container 391b1013c06ea5abe461d9474ec3b8f2c8e902e9d4b0e0cbf5ea8b8b0394541f. SELinux: mount invalid.  Same superblock, different security settings for (dev mqueue, type mqueue) Couldn't stat device /dev/char/10:200: No such file or directory Couldn't stat device /dev/char/10:200: No such file or directory Started libcontainer container 238a14cc41bdb2826850c00907c249e43b0b3333c0a344f99920adddff5c38e3. SELinux: mount invalid.  Same superblock, different security settings for (dev mqueue, type mqueue) Couldn't stat device /dev/char/10:200: No such file or directory libpod-391b1013c06ea5abe461d9474ec3b8f2c8e902e9d4b0e0cbf5ea8b8b0394541f.scope: Succeeded. libpod-391b1013c06ea5abe461d9474ec3b8f2c8e902e9d4b0e0cbf5ea8b8b0394541f.scope: Consumed 153ms CPU time Couldn't stat device /dev/char/10:200: No such file or directory Started libcontainer container 391b1013c06ea5abe461d9474ec3b8f2c8e902e9d4b0e0cbf5ea8b8b0394541f. SELinux: mount invalid.  Same superblock, different security settings for (dev mqueue, type mqueue) Couldn't stat device /dev/char/10:200: No such file or directory libpod-238a14cc41bdb2826850c00907c249e43b0b3333c0a344f99920adddff5c38e3.scope: Succeeded. libpod-238a14cc41bdb2826850c00907c249e43b0b3333c0a344f99920adddff5c38e3.scope: Consumed 160ms CPU time ... Two questions really. a) how critical those are? b) how to fix the problem? Rather obvious one. many thanks, L _______________________________________________ Podman mailing list -- podman(a)lists.podman.io To unsubscribe send an email to podman-leave(a)lists.podman.io