-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.13.0: unsuccessful cred copy: ".ssh" from "/tekton/creds" to "/root" #2791
Comments
Best, most succinct, description of creds-init I've read yet. Thanks for the issue report! |
In terms of the "hang" though - could you post the sanitized Pod YAML? The errors you have in the issue report "shouldn't" cause hangs so I'd like to try reproducing to see if I can figure out what's going wrong. |
/kind bug |
here is a dump of the pod yaml as it sits
|
There are two separate issues here:
|
Both top level |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
@tekton-robot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/remove-lifecycle rotten |
@bitsofinfo: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
any solutions to this one so far? |
Expected Behavior
I should be able to opt-out of the auto seeding of tekton creds into each step and just mount my own secrets via workspaces under
/root
. Let the user have complete control and disable some of the automatic stuff tekton does around this. For steps which use images that rely on specific things in the user's home dir (in this case/root
) I need to craft this directory in a specific way and this tekton cred stuff gets in the way.Actual Behavior
Task goes into
Error
state after 1st step. Each step in my task that does this ends up w/ this in logs. NOTE the serviceAccount this is running as has NO bound secrets.Overall in the tekton dashboard, the task just appears to be in a hung state.
Steps to Reproduce the Problem
Note I have
"disable-home-env-overwrite":"true","disable-working-directory-overwrite":"true"
/root/.ssh
My trigger workspaces:
The task def workspaces:
Additional Info
The
serviceAccount
that the pipelinerun uses, has nosecrets
attatched to it.1.16.9
The text was updated successfully, but these errors were encountered: