Latest updates fail on CentOS 7

%3CLINGO-SUB%20id%3D%22lingo-sub-2269459%22%20slang%3D%22en-US%22%3ELatest%20updates%20fail%20on%20CentOS%207%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2269459%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20been%20running%20Edge%20(dev)%20on%20all%20of%20our%20CentOS%207%20workstations%20and%20many%20servers%20for%20quite%20a%20while%20and%20been%20happy%20with%20the%20operation.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%20the%20developers%20have%20updated%20it%20to%20require%20glibc%202.18%20which%20now%20makes%20it%20incompatible%20with%20Centos%207%2C%20and%20I%20suspect%20all%20of%20the%20other%20RHEL7%20permutations.%3C%2FP%3E%3CP%3EAs%20CentOS%208%20has%20been%20aborted%20and%20CentOS%20Stream%20is%20just%20a%20bit%20too%20new%20to%20put%20into%20production%20the%20result%20is%20that%20I%20either%20just%20keep%20the%20old%20version%20or%20remove%20it%20from%20all%20devices%20which%20would%20be%20a%20bit%20of%20a%20shame.%3C%2FP%3E%3CP%3EI%20know%20I%20could%20technically%20install%20a%20later%20GLIBC%20package%20but%20these%20are%20production%20hosts%20so%20%22experimental%22%20packages%20which%20could%20cause%20any%20number%20of%20%22interesting%20effects%22%20with%20other%20packages%20are%20not%20really%20a%20good%20idea.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20Microsoft%2C%20are%20you%20going%20to%20either%20go%20back%20to%20GLIBC%202.17%2C%20statically%20link%20the%20requires%20libraries%20into%20the%20Edge%20modules%20or%20just%20drop%20support%20for%20the%20RHEL%2FCentOS%20community%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2270845%22%20slang%3D%22en-US%22%3ERe%3A%20Latest%20updates%20fail%20on%20CentOS%207%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2270845%22%20slang%3D%22en-US%22%3EThank%20you%20for%20Posting%20to%20Microsoft%20Community%2C%20Level%203%20Experts%20are%20going%20to%20help%20you%20to%20fix%20your%20problem.%20Please%20Call%20to%20support%20Team%20I~9OI~9IO~264O%3C%2FLINGO-BODY%3E
Occasional Visitor

I have been running Edge (dev) on all of our CentOS 7 workstations and many servers for quite a while and been happy with the operation.

 

Unfortunately the developers have updated it to require glibc 2.18 which now makes it incompatible with Centos 7, and I suspect all of the other RHEL7 permutations.

As CentOS 8 has been aborted and CentOS Stream is just a bit too new to put into production the result is that I either just keep the old version or remove it from all devices which would be a bit of a shame.

I know I could technically install a later GLIBC package but these are production hosts so "experimental" packages which could cause any number of "interesting effects" with other packages are not really a good idea.

 

So Microsoft, are you going to either go back to GLIBC 2.17, statically link the requires libraries into the Edge modules or just drop support for the RHEL/CentOS community?

1 Reply
Yeah, the last version that works on RHEL7 or equivalent is 96.0.1020.0. Versions after that (current version is 96.0.1032.0) require a newer glibc. Microsft did the same thing to Teams for Linux recently.

Fortunately I do not use Edge for anything but occasionally checking company websites.