fix: Fix missing disks in container

[srebhan]

Required for all PRs:

• Updated associated README.md.
• Wrote appropriate unit tests.
• Pull request title or commits are in conventional commit format

resolves #10297

This PR fixes the missing disks when trying to run telegraf from within a container.

[telegraf-tiger]

☺️ This pull request doesn't significantly change the Telegraf binary size (less than 1%)

📦 Looks like new artifacts were built from this PR.

Expand this list to get them here ! 🐯

Artifact URLs

DEB	RPM	TAR GZ	ZIP
amd64.deb	aarch64.rpm	darwin_amd64.tar.gz	windows_amd64.zip
arm64.deb	armel.rpm	darwin_arm64.tar.gz	windows_i386.zip
armel.deb	armv6hl.rpm	freebsd_amd64.tar.gz
armhf.deb	i386.rpm	freebsd_armv7.tar.gz
i386.deb	ppc64le.rpm	freebsd_i386.tar.gz
mips.deb	s390x.rpm	linux_amd64.tar.gz
mipsel.deb	x86_64.rpm	linux_arm64.tar.gz
ppc64el.deb		linux_armel.tar.gz
s390x.deb		linux_armhf.tar.gz
		linux_i386.tar.gz
		linux_mips.tar.gz
		linux_mipsel.tar.gz
		linux_ppc64le.tar.gz
		linux_s390x.tar.gz
		static_linux_amd64.tar.gz

[voiprodrigo]

After this change, logs are plagued with this type of messages:

2022-01-19T19:40:03Z D! [inputs.disk] [SystemPS] partition 0: {"device":"sysfs","mountpoint":"/sys","fstype":"sysfs","opts":["rw","nosuid","nodev","noexec","relatime"]}
2022-01-19T19:40:03Z D! [inputs.disk] [SystemPS] -> using mountpoint "/sys"...
2022-01-19T19:40:03Z D! [inputs.disk] [SystemPS] => kept...
2022-01-19T19:40:03Z D! [inputs.disk] [SystemPS] partition 1: {"device":"proc","mountpoint":"/proc","fstype":"proc","opts":["rw","nosuid","nodev","noexec","relatime"]}
2022-01-19T19:40:03Z D! [inputs.disk] [SystemPS] => dropped by filesystem-type filter
2022-01-19T19:40:03Z D! [inputs.disk] [SystemPS] partition 2: {"device":"devtmpfs","mountpoint":"/dev","fstype":"devtmpfs","opts":["rw","nosuid"]}
2022-01-19T19:40:03Z D! [inputs.disk] [SystemPS] => dropped by filesystem-type filter

[srebhan]

@voiprodrigo as you can see those are debug messages. Is there any reason you are running in debug mode?

[voiprodrigo]

@srebhan I know they're debug. Still, I feel these look as "debug during development/bug fixing", not "debugging in production". Mostly because of the buffer messages, I like to keep an eye on those.

[srebhan]

@voiprodrigo can you please open an issue to discuss possible solutions there?