部署时,Docker和"OpenSSL库报告错误"

Question

我通过Amazon Elastic Container Service通过Rust和Rocket提供API.每当我将对象放入或获取到Amazon S3时,它在本地运行良好,但如果部署在Amazon ECS上,我会收到此运行时错误:

HttpDispatch(HttpDispatchError { message: "The OpenSSL library reported an error" })

当我在我的机器上运行Docker镜像时也会发生这种情况.

我添加了错误发生的评论:

use super::types::SomeCustomType;
use rusoto_core::{DefaultCredentialsProvider, Region, default_tls_client};
use rusoto_s3::{S3, S3Client, GetObjectRequest};

pub fn load_data_from_s3(object_name: String) -> SomeCustomType {
    let credentials = DefaultCredentialsProvider::new().unwrap();
    let client = S3Client::new(default_tls_client().unwrap(), credentials, Region::UsWest2);
    let mut request = GetObjectRequest::default();
    request.bucket = "bucket-name".to_string();
    request.key = object_name.to_string();
    match client.get_object(&request) {
        // *** This is going to fail in docker container on run-time ***
        Ok(file) => {
            // this part is actually not important for this example,
            // so code has been omitted
            someCustomType
        }
        Err(e) => {
            println!("{:?}", e); // *** errors out here! ***
            SomeCustomType::default()
        }
    }
}

Cargo.toml

[dependencies]
brotli="1.0.8"
chrono = "0.3.1"
fnv = "1.0.5"
rusted_cypher = "1.1.0"
rocket = { git = "https://github.com/SergioBenitez/Rocket", rev = "614297eb9bc8fa5d9c54f653dc35b8cc3a22891f" }
rocket_codegen = { git = "https://github.com/SergioBenitez/Rocket", rev = "614297eb9bc8fa5d9c54f653dc35b8cc3a22891f" }
rocket_contrib = { git = "https://github.com/SergioBenitez/Rocket", rev = "614297eb9bc8fa5d9c54f653dc35b8cc3a22891f" }
rusoto_core = "0.25.0"
rusoto_s3 = "0.25.0"
serde = "1.0.8"
serde_json = "1.0.2"
serde_derive = "1.0.8"

这是我在macOS上构建Docker镜像的方法:

cargo clean &&
docker run -v $PWD:/volume -w /volume -t manonthemat/muslrust cargo build --release &&
docker build -t dockerimagename .

Docker图像manonthemat/muslrust基本上是clux/muslrust.我不得不建立自己的形象,因为我需要一个最近每晚构建的Rust.

这是(简化的)Dockerfile,到目前为止对我来说非常有用:

FROM scratch
ADD target/x86_64-unknown-linux-musl/release/project /
CMD ["/project"]

---

我试图解决这个问题的一些事情......

1. 添加openssl = "0.9.14"到Cargo.toml.

2. 将我的Dockerfile更改为:

   FROM alpine:edge
   
   ADD target/x86_64-unknown-linux-musl/release/project /    
   RUN apk add --no-cache curl perl openssl-dev ca-certificates linux-headers build-base zsh
   
   CMD ["/project"]
   

   这也没有改变任何东西,但给了我更多的选择来看看里面.

3. 之后我改变了交叉编译步骤cargo clean:

   docker run -v $PWD:/volume -w /volume -e RUST_LOG="rusoto,hyper=debug" -e OPENSSL_STATIC=1 -e OPENSSL_DIR=/usr/local -t manonthemat/muslrust cargo build --release --features "logging"
   

   构建新的docker镜像后,获取一个shell:

   docker run -i -e ROCKET_ENV=prod -e ROCKET_ADDRESS=0.0.0.0 -e RUST_LOG="rusoto,hyper=debug" dockerimagename /bin/zsh
   

   在那里,我通过提供一个不存在的ssl证书的不同路径来执行我的项目,但没有任何不同的效果.

   在下一次运行中,我将其设置为指向不同的路径: SSL_CERT_DIR=/etc/ssl/certs /project当打印出client.get_object(&request)调用错误时,我得到了一个有趣的结果:

   Unknown("<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<Error><Code>SignatureDoesNotMatch</Code><Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message><AWSAccessKeyId>...
   

4. 我用aws-sdk-rust箱子替换了rusoto

thread 'main' panicked at 'Error dispatching request: HttpDispatchError { message: "the handshake failed" }', /checkout/src/libcore/result.rs:860            stack backtrace:
    0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace                                                                                                            at ./checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
    1: std::sys_common::backtrace::_print                                                                                                                                  at ./checkout/src/libstd/sys_common/backtrace.rs:71
    2: std::panicking::default_hook::{{closure}}                                                                                                                           at ./checkout/src/libstd/sys_common/backtrace.rs:60
              at ./checkout/src/libstd/panicking.rs:355
    3: std::panicking::default_hook
              at ./checkout/src/libstd/panicking.rs:371
    4: std::panicking::rust_panic_with_hook
             at ./checkout/src/libstd/panicking.rs:549
    5: std::panicking::begin_panic
             at ./checkout/src/libstd/panicking.rs:511
    6: std::panicking::begin_panic_fmt
             at ./checkout/src/libstd/panicking.rs:495
    7: rust_begin_unwind
             at ./checkout/src/libstd/panicking.rs:471
    8: core::panicking::panic_fmt
             at ./checkout/src/libcore/panicking.rs:69
    9: core::result::unwrap_failed
   10: <aws_sdk_rust::aws::s3::s3client::S3Client<P, D>>::get_object
   11: himitsu::ingest::load_data_from_s3
   12: himitsu::ingest::load_data
   13: himitsu::main
   14: __rust_maybe_catch_panic
             at ./checkout/src/libpanic_unwind/lib.rs:98
   15: std::rt::lang_start
             at ./checkout/src/libstd/panicking.rs:433
             at ./checkout/src/libstd/panic.rs:361
             at ./checkout/src/libstd/rt.rs:59

5. 我在Mac上通过VirtualBox安装了Linux发行版,更新了库,安装了OpenSSL头文件并生锈,然后导入了项目.现在我马上收到SignatureDoesNotMatch错误.我确认我可以通过主机的vpn通过https访问Neo4j服务器,因此SSL似乎至少部分工作.

6. 在Amazon ECS优化的Amazon Linux AMI 2017.03.a上编译和运行项目.构建docker镜像也很有效.从该系统内部运行docker镜像不会,因为它返回时standard_init_linux.go:178: exec user process caused "no such file or directory"即使文件在那里,也具有正确的权限,可以在其上运行其他操作等等......只是不执行它.回滚到之前没有任何S3/OpenSSL依赖关系的状态时也是这种情况.这是真正的scratch和alpine基本图像.但是,如果我使用ubuntu基本映像构建docker镜像,我会运行pre-S3/OpenSSL版本.对于带有rusuto的版本,即使安装OpenSSL库及其头文件,我也会收到OpenSSL错误.

7. 在我的Mac上编译Docker镜像,推送到私人仓库到docker hub.通过ssh会话将该docker镜像拉到EC2实例上(与6中的相同).现在运行它并没有像6中那样给出"没有这样的文件或目录"错误,但是好的ol' HttpDispatch(HttpDispatchError { message: "The OpenSSL library reported an error" })(现在甚至在将SSL_CERTS_DIR =/etc/ssl/certs传递到容器的环境中时)

Answer 1

这些是我为在 AWS 上进行部署而采取的步骤。

我确信有方法可以优化这一点，我将编辑这篇文章，因为我将了解有关该过程的更多信息，但这些是我已采取的步骤。

1. 我在 macOS 上构建了二进制文件：

   docker run -v $PWD:/volume -w /volume -e RUST_LOG="rusoto,hyper=debug" -e OPENSSL_STATIC=1 -e OPENSSL_DIR=/usr/local -e SSL_CERT_DIR=/etc/ssl/certs -t manonthemat/muslrust cargo build --release --features "logging"

2. 我修改了 Dockerfile

   FROM alpine:edge COPY target/x86_64-unknown-linux-musl/release/project / RUN apk update && apk add --no-cache pkgconfig openssl-dev ca-certificates linux-headers && update-ca-certificates CMD [ "/project" ]

3. 我构建了 docker 镜像

   • 然后，我将 docker 映像推送到私有存储库，并通过 EC2 实例上的 ssh-session 将其拉出以进行测试。我通过以下方式成功运行了它docker run -e SSL_CERT_DIR=/etc/ssl/certs secretuser/secretrepo:notsosecrettag

4. 我标记了 docker 镜像并将其推送到 AWS 存储库

5. 为了在 Amazon Elastic Container Service 上成功运行，我必须修改任务定义。在containerDefinitions中，我必须增加内存并将其添加到环境数组中：

   `{
     "name": "SSL_CERT_DIR",
     "value": "/etc/ssl/certs"
   }`
   

6. 由于某些未知且可能不相关的原因，我还必须更新 EC2 实例上的代理，然后重新启动这些代理。