Description of problem:

Hi,

I am running BuildConfig with s2i strategy on OKD 3.9 cluster and I am getting error:

```
{"message":"Error processing tar file(exit status 1): invalid symlink \"/tmp/..data\" -> \"..2019_08_06_16_00_26.551658995\""}
ERROR: Error occurred during injecting "/var/run/secrets/openshift.io/build/maven-setting" to "/tmp": Error response from daemon:

{"message":"Error processing tar file(exit status 1): invalid symlink \"/tmp/..data\" -> \"..2019_08_06_16_00_26.551658995\""}
```

My BuidConfig is:

```
apiVersion: build.openshift.io/v1
kind: BuildConfig
spec:
  source:
    secrets:
      - destinationDir: /tmp
        secret:
          name: maven-setting
```

Version of Docker daemon on compute node with failed build:

```
 Package version: docker-1.13.1-102.git7f2769b.el7.centos.x86_64
 Go version:      go1.10.3
```

Errors don`t occurs when I roll back docker package version to the older version:

```
Package version: docker-1.13.1-88.git07f3374.el7.centos.x86_64
 Go version:      go1.9.4
```

I found that it is due to this issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1714722

Any plans to fix s2i secrets injection with CVE-2018-15664 fix in docker package?


Version-Release number of selected component (if applicable): OKD 3.9


Additional info:

Originally reported on Github: https://github.com/openshift/source-to-image/issues/987