micro: GLIBC Errors in 2.0.14-rc1 and 2.0.14

Description of the problem or steps to reproduce

I attempted to update from linux64 release 2.0.13 by removing the binary and running the installation script, which installed linux64 release 2.0.14. Executing the new binary produces the following errors:

./micro: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.32’ not found (required by ./micro) ./micro: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.34' not found (required by ./micro)

Manually-downloaded and extracted binaries for linux64 release 2.0.14 and linux64 release 2.0.14-rc1 produce the same errors.

Redownloading linux64 release 2.0.13 resolved the errors.

Specifications

Versions: 2.0.14 and 2.0.14-rc1 Commit hashes: 04c5770 and cc195b6 OS: Ubuntu 20.04.6 LTS

ldd --version ldd (Ubuntu GLIBC 2.31-0ubuntu9.16) 2.31

I’m still a bit of a novice with Linux and programming, so let me know if I’ve left anything out or did anything wrong above. As far as I’ve been able to discover, GLIBC is system-dependent, so I can’t really upgrade to the newer required versions. The only way to do that would be to upgrade from Ubuntu 20.04 to a newer version, which I can do if the new requirement is intentional and necessary. I understand if Ubuntu 20.04 is too old of a version to support anymore, but there was nothing advising of a minimum GLIBC/OS version.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 18 (4 by maintainers)

Most upvoted comments

We have a nice mess here as a matter of fact: the editor itself being maintained in one repo, its sub-projects like forked tcell maintained in other repos, its webpage maintained in yet another repo, its installation script recommended on the webpage maintained in yet another repo, - and none of the parties maintaining any of the aforementioned repos having control over all other repos.

I think this is none of your fault. It is newer Go versions that require a newer minimum glibc version, and our fault that we released 2.0.14 built with Go 1.19, without realizing that it will not work on systems with older glibc (some of which are still not very old, e.g. Ubuntu 20.04 is still LTS supported, as I understand). I’m not sure which Go version was micro 2.0.13 built with, but probably it was older than 1.19, since it works for you.

Fortunately 2.0.14 also includes a fully static version of micro binary: micro-2.0.14-linux64-static.tar.gz. It doesn’t have any external dependencies on glibc or any other libraries, so it should work for you without problems.

For me as an uninitiated user, I don’t expect much additional risk from the install script than from running micro itself, as there’s a level of trust that has to be given to the developers when using any software.

It’s not just about trusting the code you run, it’s also about trusting the way how you run (and download) this code. You begin executing the script before even fully downloading it. What if the network connection drops in the middle? And so on.

I think it’s reasonable to just make all builds fully static by default, at least when built by the GitHub actions runner. Go has improved some of the issues with disabling cgo in recent years (the pure-go DNS resolver used to have some problems) and all non-linux builds are already all fully static anyway because they are cross-compiled.

I knew that the static version existed but had no idea what it was for.

I’d rather wonder what do we need the dynamic version for, if the static one works just fine. This is what micro’s readme says about it: “By default, the micro binary will dynamically link with core system libraries (this is generally recommended for security and portability).”

Regarding the security argument, I think in your case there’s nothing to worry about, since the static micro 2.0.14 binary was built with a newer glibc version than you have, so all glibc security fixes you have in your glibc should even more so be present in this static binary as well.

Regarding portability/compatibility concerns, as long as micro works fine for you, again, nothing to bother about.

While I was looking through the installer script at https://getmic.ro (I’m not sure where that is maintained but it doesn’t seem to be here)

It is indeed maintained in a separate repo https://github.com/benweissmann/getmic.ro, by @benweissmann, not by micro maintainers.

I wonder if in addition to the check for the musl libc, it could also check for the installed version of glibc and direct to the static version if the installed glibc version is too low. This would help out people in a similar position to me not have to engage in manual installation when using an automated script.

It is not immediately obvious to me how to implement this check (i.e. how to find out which minimum version of glibc is required), but maybe it is not too difficult. @benweissmann what do you think?