Closed avahahn closed 1 month ago
Does the move to hyper-rustls mean that the resulting binary will not be linked to openssl anymore?
Does the move to hyper-rustls mean that the resulting binary will not be linked to openssl anymore?
Yes. I verified this with ldd on x86_64.
This PR contains commits to fix both https://github.com/nginx/unit/issues/1439 and https://github.com/nginx/unit/issues/1438.
The OpenSSL issue is solved by moving to hyper-rustls from hyper-tls.
The docker client error (hyper legacy client connect error) is solved by bumping the bollard library version and also just in case I have elaborated on the error print text.
Both issues were tested on Debian latest docker image (x86_64) as well as M1 (aarch64) OSX. Help verifying on an aarch64 Linux box is welcome, but I expect similar results.