Closed phanirajkiran closed 1 year ago
See https://github.com/docker-library/busybox/issues/155#issuecomment-1341490383:
The libc packaged within this image is intended to support BusyBox (which cannot be compiled without a suitable libc implementation, and whose behavior differs slightly based on the libc implementation), and is not explicitly intended for external use (anything like that which "works" is incidental). I would expect more incompatibilities in the future.
(Our current build of glibc itself comes from Debian Bullseye, but will not necessarily continue to come from Debian or even Debian Bullseye specifically.)
@tianon Thanks for quick response! Great Support.
How do i build this busybox source ?. I want to keep /var/lib .
Thanks Phani
Unfortunately, these issues are not a general support forum -- I'd suggest trying a dedicated support forum, such as the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow.
Hi, I want to know does the docker image arm32v7/busybox:glibc supports dynamically linked run time binaries?
Or
How to make a docker image arm32v7/busybox:glibc to support ldd (dynamically loading of libraries (.so) ) ? where i need to add to support this ?
Thanks Phani