On a centos7 server I'm getting this, but glibc 2.17 is the stable version on centos7

<core_client_version>7.7.0</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)
</message>
<stderr_txt>
../../projects/www.mlcathome.org_mlcathome/mlds_0.90_x86_64-pc-linux-gnu: /lib64/libc.so.6: version `GLIBC_2.18' not found (required by /tmp/.mount_mlds_0MyssxK/usr/bin/../lib/libstdc++.so.6)

</stderr_txt>
]]>

Hmm, I thought I had chased down all those. Let me reproduce here and try to fix. Are you running a CentOS 7 point release, or straight CentOS 7? Thank you for trying!

It's a fairly straight Centos7, some additional libraries from a few experimental repos.

I may try an inline upgrade to 8, which though not supported officially, might work.

I doubt you'll be the only CentOS 7 user, so I'll need to fix it up regardless.

Thanks for working on this. I have the same problem
CentOS Linux release 7.7.1908 (Core)

---

The problem is pytorch doesn't really support static linking, and I build the binary on ubuntu 14.04 thinking that would be old enough.. it uses glibc2.19, and centos 7 uses glibc 2.17. AppImage doesn't allow including glibc in its container though, so I'll need to build on an earlier distro.

But.. earlier versions of ubuntu/debian don't have ready-made gcc-9 or libhdf5 packages, and centos 7 doesn't either. Meaning.. i have to compile those from source, meaning it might take a day or so. Thanks for your patience.

Hate to do this to you, but I've just loaded 0.911, which will now disable centos 7 support again.. compiling with that old a libc caused more and more crashes on other systems. I'll head back to the drawing board there.

Any progress on this issue or did you give up on CentOS 7 ?

<core_client_version>7.16.6</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)</message>
<stderr_txt>
../../projects/www.mlcathome.org_mlcathome/mlds_9.61_x86_64-pc-linux-gnu: /lib64/libc.so.6: version `GLIBC_2.18' not found (required by ../../projects/www.mlcathome.org_mlcathome/mlds_9.61_x86_64-pc-linux-gnu)
../../projects/www.mlcathome.org_mlcathome/mlds_9.61_x86_64-pc-linux-gnu: /lib64/libc.so.6: version `GLIBC_2.18' not found (required by /tmp/.mount_mlds_927A58Y/usr/bin/../lib/libstdc++.so.6)

</stderr_txt>
]]>

Running CentOS Linux release 7.8.2003

Tom

I don't think CentOS 7 support is going to happen, unfortunately. I know that's not something you'd like to hear, but after we compiled a client with that old a libc version the average error rate on all our clients jumped three times higher than the rate with our current setup. It would take some time and effort to figure out why, and CentOS 7 is already 6 years old.

Like I mentioned in the news thread, we need to be a bit better about posting minimum requirements up front.

Why not upgrade from CentOS 7 to CentOS 8 or 9? CentOS 8 has GLIBC 2.28, CentOS 9 even has GLIBC 2.34.

Any progress on this issue or did you give up on CentOS 7 ?....Running CentOS Linux release 7.8.2003. Tom

Try running CentOS Linux 8.5.2111

Actually, the new CPU client should work fine on CentOS 7, because it's statically linked. GPU clients are still an issue though since they are not.