This just started happening today, but I cannot identify a cause.
Pipeline script involving sh inside a Dockerfile agent.

stage('Test') {
  agent {
    dockerfile {
      additionalBuildArgs "--tag jenkins/${dockerName}:${BRANCH_NAME}"
      args '--cap-add=SYS_ADMIN'
      reuseNode true
    }
  }
  environment {
    NG_PORT = PortAllocator.get()
  }
  steps {
    sh 'npm run --silent -- lint --force --format=checkstyle >checkstyle-result.xml'
    // ...

Job fails with

process apparently never started in /var/lib/jenkins/node/workspace/JOBNAME@tmp/durable-eb571b59
...
ERROR: script returned exit code -2

The following is in the system log

dockerd-current: time="2019-10-25T17:23:12.299653636+01:00" level=error msg="Error running exec in container: rpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused \"exec: \\"/var/lib/jenkins/node/caches/durable-task/durable_task_monitor_1.31_unix_64
": stat /var/lib/jenkins/node/caches/durable-task/durable_task_monitor_1.31_unix_64: no such file or directory\"\n"

That file exists and is executable

$ ls -la /var/lib/jenkins/node/caches/durable-task/
total 2512
drwxrwxr-x 2 jenkins jenkins    4096 Oct 25 15:26 .
drwxrwxr-x 3 jenkins jenkins    4096 Oct 25 15:26 ..
-rwxr-xr-x 1 jenkins jenkins 2561975 Oct 25 15:26 durable_task_monitor_1.31_unix_64