-
Notifications
You must be signed in to change notification settings - Fork 180
Closed
Description
The buildkit feature of bollard includes the ssl feature, which includes rustls/ring. This results in ring being brought into dependencies even if the aws-lc-rs feature is selected. A workaround is to call CryptoProvider::install_default(), but that is less than ideal since ring shouldn't be brought into the dependencies at all if aws-lc-rs is chosen.
bollard #docker
An asynchronous Docker daemon API
version: 0.19.1 (latest 0.19.2)
license: Apache-2.0
rust-version: unknown
documentation: https://docs.rs/bollard
homepage: https://github.com/fussybeaver/bollard
repository: https://github.com/fussybeaver/bollard
crates.io: https://crates.io/crates/bollard/0.19.1
features:
default = [http, pipe]
...
aws-lc-rs = [ssl_providerless, rustls/aws-lc-rs]
bollard-buildkit-proto = [dep:bollard-buildkit-proto]
buildkit = [chrono, num, rand, tokio/fs, tokio-stream, tokio-util/io, tonic, tower-service, ssl, bollard-stubs/buildkit, bollard-buildkit-proto, dep:async-stream, dep:bitflags]
...
ssh = [hyper-util, openssh, tower-service]
ssl = [ssl_providerless, rustls/ring]
...
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels