Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Unable to execute builds with secrets as part of the configuration. 

- build fails on adding the secret to the build:
error: Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink "/opt/app-root/src/..data" -> "..2019_08_06_22_44_01.875817706"
ERROR: Error occurred during injecting "/var/run/secrets/openshift.io/build/secret" to "/opt/app-root/src": Error response from daemon: Error processing tar file(exit status 1): invalid symlink "/opt/app-root/src/..data" -> "..2019_08_06_22_44_01.875817706"


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

atomic-openshift-3.11.98-1.git.0.0cbaff3.el7.x86_64
docker-1.13.1-102.git7f2769b.el7.x86_64
docker-client-1.13.1-102.git7f2769b.el7.x86_64
docker-common-1.13.1-102.git7f2769b.el7.x86_64

How reproducible:

Attached the buildconfig to the bug. Include the secrets as part of the build. 


Actual results:

Build fails with the error in the description. 

Additional info:

-> Downgrading the version helps to resolve the issue. The same bc works fine with a lower version of docker (96 for example) and fails for 102.

Related to https://bugzilla.redhat.com/show_bug.cgi?id=1738599.

*** Bug 1738599 has been marked as a duplicate of this bug. ***

Bug also impacts 3.9 and 3.10 (and earlier, though these versions have reached EOL). Updating impacted version.

So the original CVE fix 
has been cited as a regression upstream, noted via https://github.com/moby/moby/issues/39348 and the subsequent fixes from https://github.com/docker/engine/pull/275 and https://github.com/moby/moby/pull/39357 and https://github.com/docker/engine/pull/280

We are testing against 1.13.1-102

We need to determine what RHEL Docker level has https://github.com/docker/engine/pull/275 and https://github.com/moby/moby/pull/39357 and https://github.com/docker/engine/pull/280

I have confirmed that https://github.com/moby/moby/pull/39357 is not in https://github.com/projectatomic/docker/commits/docker-1.13.1-rhel and https://github.com/projectatomic/docker/blob/docker-1.13.1-rhel/

Sending it over to rhel7/docker ... what is the status of fixing the regressions introduced by https://github.com/moby/moby/pull/39292 ... do we know yet what version of the docker RPMs after 1.13.1-102 will have the fix?

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:3092