centos 6 asset is not fully compatible with centos 6

[cwjohnston]

Expected behavior

The Centos 6 asset is able to run ruby code using native extensions compiled against Centos 6 glibc.

Current behavior

The centos 6 asset errors when running ruby code using native extensions.

Reproduction steps

1. Stand up a Centos 6.10 host running the Sensu agent
2. Add assets for version 0.0.10 of sensu-ruby-runtime for centos 6 and version 5.0.0 of sensu-plugins-disk-checks
3. add a check which uses those runtime assets, with check-disk-usage.rb
4. Observe that the check results show an error related to GLIBC_VERSION 2.14 not found -- centos 6.10 is expected to have GLIBC version 2.12

Context

I feel like I've run into similar behavior in the past where using Docker containers to compile binaries for platforms with one version of glibc actually results in binaries linked to the docker host glibc. It might be the case that we cant use Docker for our build process here?

[jspaleta]

I think case of sensu-plugins-disk-checks, it looks like it was not rebuilt after the glibc issues were sorted out in the ruby runtime. To work on centos6, assets need to offer an explicit centos6 build.

I'm spinning up a update for sensu-plugins-disk-checks in my namespace now as a test to make sure I'm right.

Probably what we need to do is review/update the .bonsai.yml for the existing sensu-plugins that have assets and respin them all in one push to make sure we have centos6 builds for all the existing ones.

[jspaleta]

Cna you retest with latest sensu-plugins-disk-checks. There is now an explicit centos6 build for that plugin

[yusufyildiz]

this is still an issue.