whitebox_tools requires GLIBC 2.32 or higher #55
Replies: 1 comment
-
It is because One temporary solution is that you pull the WBT backend from the URL below. It is the one I built using Ubuntu 18.04 with an older version of GLIBC so that users can use it with Google Colab. In your docker, you download this zip file and unzip it to your whitebox package installation directory, e.g., |
Beta Was this translation helpful? Give feedback.
-
Hi folks,
We have a docker container and we simply have whitebox via pip and it has worked for months. Starting somewhere between Wednesday night and yesterday, all our of servers and containers are now erroring out on whitebox. We are just using the simple python whitebox package, which appears to call out to get whitebox_tools on demand.
The errors:
(short form): ./whitebox_tools: /lib/x86_64-linux-gnu/libc.so.6: version 'GLIBC_2.35' not found (required by ./whitebox_tools)
We get four of these lines (one for GLIBC 2.32 to 2.35).
We have played with set_whitebox_dir. We have a couple of us looking into this for two days and am out of ideas.
We do want to upgrade GLIBC (too many side effects). We have checked permissions, updates Ubuntu updates that might have triggered this problem starting last week. We tried dropping from whitebox 2.2.0, 2.0.0 and the 2.3.0 (that was released today). We do not pull down and pre-compile the WBT engine??? but maybe we need to do it.
Any guesses on why it is suddenly stopped?
And how do we fix it?
Rob
Beta Was this translation helpful? Give feedback.
All reactions