Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: tidb-dashboard 的依赖包版本太高是基于什么原因导致的这个现象呢？
[TiDB Usage Environment] Poc
[TiDB Version] v6.5.0
[Reproduction Path] tidb-dashboard deployment
[Encountered Issues: Problem Phenomenon and Impact]
Recently, there have been many posts, including my own, encountering issues when installing and deploying tidb-dashboard. In summary, it seems that the dependency package version of tidb-dashboard is too high. I would like to understand the reason for binding such a high version. Is it due to some cool presentation method or the need for more efficient underlying communication?
I don’t understand why a high version of glibc is required. Generally, system dependencies like this are compatible with version 2.17. Upgrading to a higher version can cause various other software errors and may even lead to system reboot failures. If high and low versions coexist and the specification fails, it can also cause various other issues.
At present, it seems that the official team used a system with a higher version of glibc to compile the release bin package, and lower version systems cannot run binaries generated by higher versions.
I will test it this afternoon to see if it can be successfully compiled on a system with a lower version of glibc.
Because we used a different base image builder from the core components like PD and TiDB during our CD process, the glibc version is not compatible with the minimum required version of the kernel.
I posted the answer from my other thread here.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: 数据小黑
|
username: 
|
username: