Error when building the image

[torangel]

I was hoping to use this image when testing pdf-tools signing software from a .netcore container. The problem is that the image doesn't build correct. Part of the log is shown below. The complete log is available here: log.txt

I would very much appreciate some directions on how to get this working :)

Processing triggers for sgml-base ...
Cloning into 'pkcs11-proxy'...
Note: checking out '0caa567d78a6d88365946399b68e3327969f3bff'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at 0caa567... Update seccomp usage to version 2.1.0 (Ubuntu 14.04).
[detached HEAD 2de1638] opt out of seccomp
 Author: Leif Johansson <[email protected]>
 5 files changed, 20 insertions(+)
[detached HEAD f953335] super important fix from jacob
 Author: Leif Johansson <[email protected]>
 1 file changed, 1 insertion(+)
../pkcs11-proxy.diff:11: trailing whitespace.
target_link_libraries (pkcs11-proxy pthread_nonshared ssl crypto c_nonshared)
../pkcs11-proxy.diff:12: trailing whitespace.
target_link_libraries (pkcs11-daemon dl pthread ssl crypto)
../pkcs11-proxy.diff:25: trailing whitespace.
Build-Depends: cdbs, debhelper (>= 6), cmake, libssl-dev (>= 1.0.0)
../pkcs11-proxy.diff:37: trailing whitespace.
                if (!path || !path[0]) {
../pkcs11-proxy.diff:38: trailing whitespace.
                        path = getenv("PKCS11_PROXY_PORT");
error: patch failed: CMakeLists.txt:33
error: CMakeLists.txt: patch does not apply
error: patch failed: debian/control:2
error: debian/control: patch does not apply
error: patch failed: gck-rpc-module.c:1353
error: gck-rpc-module.c: patch does not apply
The command '/bin/sh -c apt-get -y update

[darconeous]

I haven't messed with this container in a while. I was originally trying to get it up and running to help prevent container compromise from leading to the compromise of the private X509 keys.

This is way outside of my radar at the moment, and will remain that way for the foreseeable future. Sorry about that.