Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

openssl libraries for tpm2-openssl are wrong #7

Open
iolivergithub opened this issue Apr 14, 2021 · 1 comment
Open

openssl libraries for tpm2-openssl are wrong #7

iolivergithub opened this issue Apr 14, 2021 · 1 comment

Comments

@iolivergithub
Copy link
Contributor

Currently commented out in the Dockerfile.release. During the compile of the tpm2-openssl I get this error. Tried solving it using libssl-dev but seems not to work. Wouldn't like to specifically compile openssl into this but it is an option. If anyone has a better idea then please solve :-)

So, libssl-dev is the wrong version:

RUN apt update -yq && \
    DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true \
  apt -y install libssl-dev

Error from ./compile here:

#34 9.558 checking for CRYPTO... no
#34 9.565 configure: error: Package requirements (libcrypto >= 3.0.0) were not met:
#34 9.565 
#34 9.565 Requested 'libcrypto >= 3.0.0' but version of OpenSSL-libcrypto is 1.1.1f
#34 9.565 
#34 9.565 Consider adjusting the PKG_CONFIG_PATH environment variable if you
#34 9.565 installed software in a non-standard prefix.
#34 9.565 
#34 9.565 Alternatively, you may set the environment variables CRYPTO_CFLAGS
#34 9.565 and CRYPTO_LIBS to avoid the need to call pkg-config.
#34 9.565 See the pkg-config man page for more details.
------
failed to solve with frontend dockerfile.v0: failed to build LLB: executor failed running [/bin/sh -c ./bootstrap &&     ./configure &&     make &&     make install]: runc did not terminate sucessfully
make: *** [Makefile:39: all] Error 1

@tomoveu
Copy link
Collaborator

tomoveu commented Apr 16, 2021

This seems like a tpm2-openssl issue with Ubuntu versioning of OpenSSL. I do not think this is a Docker issue. I may be wrong.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants