adonis0147 opened a new issue, #24838:
URL: https://github.com/apache/doris/issues/24838

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Version
   
   Version: master (Built in docker environment)
   OS: CentOS 6
   
   ### What's Wrong?
   
   ```shell
   ❯ ldd doris_be
   ./doris_be: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by 
./doris_be)
           linux-vdso.so.1 =>  (0x00007ffe70ac8000)
           libresolv.so.2 => /lib64/libresolv.so.2 (0x00007efc550ee000)
           librt.so.1 => /lib64/librt.so.1 (0x00007efc54ee6000)
           libc.so.6 => /lib64/libc.so.6 (0x00007efc54b54000)
           /lib64/ld-linux-x86-64.so.2 (0x00007efc6c674000)
           libm.so.6 => /lib64/libm.so.6 (0x00007efc548d0000)
           libdl.so.2 => /lib64/libdl.so.2 (0x00007efc546cc000)
           libz.so.1 => /lib64/libz.so.1 (0x00007efc544b6000)
           libpthread.so.0 => /lib64/libpthread.so.0 (0x00007efc54299000)
   ```
   
   ### What You Expected?
   
   Run `doris_be` successfully.
   
   ### How to Reproduce?
   
   ```
   docker run -it --rm --mount=type=bind,source="$(pwd)",target=/doris 
apache/doris:build-env-ldb-toolchain-latest
   cd /doris
   ./build.sh --be --clean -j "$(nproc)"
   ```
   
   ### Anything Else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to