[
https://issues.apache.org/jira/browse/MINIFI-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135401#comment-16135401
]
ASF GitHub Bot commented on MINIFI-388:
---------------------------------------
Github user phrocker commented on a diff in the pull request:
https://github.com/apache/nifi-minifi-cpp/pull/131#discussion_r134278103
--- Diff: docker/Dockerfile ---
@@ -100,6 +100,10 @@ RUN mkdir -p $MINIFI_BASE_DIR
COPY --from=builder ${MINIFI_HOME} ${MINIFI_HOME}
RUN chown -R ${USER}:${USER} /opt/minifi
+# Link crypto libs to known locations for civet
+RUN ln -s /usr/lib/libcrypto.so.1.0.0 /usr/lib/libcrypto.so
--- End diff --
why not set the make option with CIVET? It seems like a bandaid that could
come apart if something within the container changed. Could it be such that our
make CRYPTO_LIB was determined via an embedded command?
> MiNiFi core on startup if TLS is used with ListenHTTP (civet)
> -------------------------------------------------------------
>
> Key: MINIFI-388
> URL: https://issues.apache.org/jira/browse/MINIFI-388
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: C++, Docker
> Reporter: Andrew Christianson
> Assignee: Andrew Christianson
>
> MiNiFi cpp core dumps on startup because civet attempts to load
> libssl/libcrypto from non-versioned paths (/usr/lib/libssl.so,
> /usr/lib/libcrypto.so). This is simple to fix with symlinks from 1.0.0 lib
> paths to the non-versioned paths.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
