[jboss-jira] [JBoss JIRA] (WFWIP-177) Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink

[Ken Wills (Jira)]

    [ https://issues.jboss.org/browse/WFWIP-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13772750#comment-13772750 ] 

Ken Wills edited comment on WFWIP-177 at 8/20/19 1:24 AM:
----------------------------------------------------------

[~mchoma] I've mounted the secret as part of the buildconfig and it appears to work find, though the builder pod completes so quickly I can't actually verify the secret is present in the pod. I'll have to try a longer running version in the morning and verify it is present.

I don't see any reason why there would be a permissions issue when mounting it though, and there is nothing obvious missing from the UBI 7 image (tar etc).

Do you have any more info on how this is all set up and triggered? If its in the testsuite, could you link me the test?



was (Author: luck3y):
[~mchoma] I've mounted the secret as part of the buildconfig and it appears to work find, though the builder pod completes so quickly I can't actually verify the secret is present in the pod. I'll have to try a longer running version in the morning and verify it is present.

I don't see any reason why there would be a permissions issue when mounting it though, and there is nothing obvious missing from the UBI 7 image (tar etc).

> Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFWIP-177
>                 URL: https://issues.jboss.org/browse/WFWIP-177
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: OpenShift
>            Reporter: Martin Choma
>            Assignee: Ken Wills
>            Priority: Major
>
> Use case is providing settings.xml as secret. I wonder if this could be some ubi7 file permission issue. 
> {code}
> Receiving source from STDIN as archive ...
> Using docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD-3331 as the s2i builder image
> error: Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink "/etc/test-secret/..data" -> "..2019_08_19_13_20_57.538692366"
> ERROR: Error occurred during injecting "/var/run/secrets/openshift.io/build/test-secret" to "/etc/test-secret": Error response from daemon: Error processing tar file(exit status 1): invalid symlink "/etc/test-secret/..data" -> "..2019_08_19_13_20_57.538692366"
> error: build error: non-zero (13) exit code from docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD-3331
> {code}
> {code:yaml|title=BuildConfig}
> apiVersion: build.openshift.io/v1
> kind: BuildConfig
> metadata:
>   creationTimestamp: '2019-08-19T13:20:41Z'
>   name: sti-secret-settings
>   namespace: mchoma
>   resourceVersion: '1345248'
>   selfLink: >-
>     /apis/build.openshift.io/v1/namespaces/mchoma/buildconfigs/sti-secret-settings
>   uid: 249b6a94-c284-11e9-b93c-fa163e9a0fb6
> spec:
>   failedBuildsHistoryLimit: 5
>   nodeSelector: {}
>   output:
>     to:
>       kind: ImageStreamTag
>       name: 'sti-secret-settings:latest'
>   postCommit: {}
>   resources: {}
>   runPolicy: Serial
>   source:
>     binary: {}
>     secrets:
>       - destinationDir: /etc/test-secret
>         secret:
>           name: test-secret
>     type: Binary
>   strategy:
>     sourceStrategy:
>       env:
>         - name: MAVEN_ARGS
>           value: install -s /etc/test-secret/settings.xml
>       from:
>         kind: DockerImage
>         name: >-
>           docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD-3331
>       incremental: false
>     type: Source
>   successfulBuildsHistoryLimit: 5
>   triggers:
>     - generic:
>         allowEnv: true
>         secret: secret101
>       type: Generic
> status:
>   lastVersion: 1
> {code}
> {code:yaml|title=Secret}
> apiVersion: v1
> data:
>   settings.xml: >-
>     PHNldHRpbmdzPgogPHByb2ZpbGVzPiAgPHByb2ZpbGU+ICAgICA8aWQ+dGVzdDwvaWQ+ICAgICA8cmVwb3NpdG9yaWVzPiAgICAgICA8cmVwb3NpdG9yeT4gICAgICAgICA8aWQ+RUFQLTc8L2lkPiAgICAgICAgIDxuYW1lPkVBUDcgcmVwbzwvbmFtZT4gICAgICAgICA8dXJsPmh0dHBzOi8vbWF2ZW4ucmVwb3NpdG9yeS5yZWRoYXQuY29tL2dhLzwvdXJsPiAgICAgICA8L3JlcG9zaXRvcnk+ICAgICA8L3JlcG9zaXRvcmllcz4gICA8L3Byb2ZpbGU+ICA8L3Byb2ZpbGVzPiAgPGFjdGl2ZVByb2ZpbGVzPiAgICA8YWN0aXZlUHJvZmlsZT50ZXN0PC9hY3RpdmVQcm9maWxlPiA8L2FjdGl2ZVByb2ZpbGVzPiA8L3NldHRpbmdzPg==
> kind: Secret
> metadata:
>   creationTimestamp: '2019-08-19T13:20:41Z'
>   name: test-secret
>   namespace: mchoma
>   resourceVersion: '1345244'
>   selfLink: /api/v1/namespaces/mchoma/secrets/test-secret
>   uid: 246843e8-c284-11e9-b93c-fa163e9a0fb6
> type: Opaque
> {code}



--
This message was sent by Atlassian Jira
(v7.12.1#712002)