[JIRA] (JENKINS-41418) Permission denied while accessing workspace
Title: Message Title
Madhura Dhananjaya updated an issue
Jenkins / JENKINS-41418
Permission denied while accessing workspace
Change By:
Madhura Dhananjaya
Comment:
Hi I have a similar issue on reading a shell script from jenkins it says Permission denied. Im using a user as root > git rev-parse refs/remotes/origin/alva-6308^\{commit} # timeout=10*14:18:55*> git rev-parse refs/remotes/origin/origin/alva-6308^\{commit} # timeout=10*14:18:55*> git config core.sparsecheckout # timeout=10*14:18:55*> git checkout -f 25ac94a8cf190640ef0c6375f923aac17e07a9ab # timeout=10*14:18:55*> git rev-list --no-walk 595cc8a05be707ec2f50d156f331f17f65919656 # timeout=10[Pipeline] readYaml[Pipeline] stage[Pipeline] { (Read and execute terraform modules)[Pipeline] script[Pipeline]{[Pipeline] dir*14:18:56* Running in /home/jenkins/workspace/alva/newrelic_terraform_testing/dev/terraform/newrelic/container_policies[Pipeline]{[Pipeline] withCredentials*14:18:56* Masking supported pattern matches of $MCS_NONPROD_CORP[Pipeline]{[Pipeline] sh*14:18:56* + ./terraform-newrelic-init.sh *14:18:56* */home/jenkins/workspace/alva/newrelic_terraform_testing/dev/terraform/newrelic/container_policies@tmp/durable-1125f127/script.sh: line 2: ./terraform-newrelic-init.sh: Permission denied* Can someone suggest on this? I am blocked with this. Where can I set permissions to read shell script?
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-41418) Permission denied while accessing workspace
Title: Message Title Carlos Sanchez commented on JENKINS-41418 Re: Permission denied while accessing workspace please do not ask questions in closed issues. Use the jenkins-user mailing list Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178200.1485341884000.3507.1585646580450%40Atlassian.JIRA.
[JIRA] (JENKINS-41418) Permission denied while accessing workspace
Title: Message Title
Madhura Dhananjaya edited a comment on JENKINS-41418
Re: Permission denied while accessing workspace
Hi I have a similar issue on reading a shell script from jenkins it says Permission denied. Im using a user as root ('--net=host -v /var/run/docker.sock:/var/run/docker.sock:rw --entrypoint="" --user root') > git rev-parse refs/remotes/origin/alva-6308^\{commit} # timeout=10*14:18:55* > git rev-parse refs/remotes/origin/origin/alva-6308^\{commit} # timeout=10*14:18:55* > git config core.sparsecheckout # timeout=10*14:18:55* > git checkout -f 25ac94a8cf190640ef0c6375f923aac17e07a9ab # timeout=10*14:18:55* > git rev-list --no-walk 595cc8a05be707ec2f50d156f331f17f65919656 # timeout=10 [Pipeline] readYaml readYaml [Pipeline] stage [Pipeline] { (Read and execute terraform modules) [Pipeline] script [Pipeline] {[Pipeline] dir *14:18:56* Running in /home/jenkins/workspace/alva/newrelic_terraform_testing/dev/terraform/newrelic/container_policies[Pipeline] {[Pipeline] withCredentials *14:18:56* Masking supported pattern matches of $MCS_NONPROD_CORP [Pipeline] {[Pipeline] sh*14:18:56* + ./terraform-newrelic-init.sh *14:18:56* */home/jenkins/workspace/alva/newrelic_terraform_testing/dev/terraform/newrelic/container_policies@tmp/durable-1125f127/script.sh: line 2: ./terraform-newrelic-init.sh: Permission denied* Can someone suggest on this? I am blocked with this. Where can I set permissions to read shell script?
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Is
[JIRA] (JENKINS-41418) Permission denied while accessing workspace
Title: Message Title
Madhura Dhananjaya commented on JENKINS-41418
Re: Permission denied while accessing workspace
Hi I have a similar issue on reading a shell script from jenkins it says Permission denied. Im using a user as root ('-net=host -v /var/run/docker.sock:/var/run/docker.sock:rw entrypoint="" -user root') > git rev-parse refs/remotes/origin/alva-6308^{commit} # timeout=10*14:18:55* > git rev-parse refs/remotes/origin/origin/alva-6308^{commit} # timeout=10*14:18:55* > git config core.sparsecheckout # timeout=10*14:18:55* > git checkout -f 25ac94a8cf190640ef0c6375f923aac17e07a9ab # timeout=10*14:18:55* > git rev-list --no-walk 595cc8a05be707ec2f50d156f331f17f65919656 # timeout=10[Pipeline] readYaml[Pipeline] stage[Pipeline] { (Read and execute terraform modules)[Pipeline] script[Pipeline] {[Pipeline] dir*14:18:56* Running in /home/jenkins/workspace/alva/newrelic_terraform_testing/dev/terraform/newrelic/container_policies[Pipeline] {[Pipeline] withCredentials*14:18:56* Masking supported pattern matches of $MCS_NONPROD_CORP[Pipeline] {[Pipeline] sh*14:18:56* + ./terraform-newrelic-init.sh 14:18:56 /home/jenkins/workspace/alva/newrelic_terraform_testing/dev/terraform/newrelic/container_policies@tmp/durable-1125f127/script.sh: line 2: ./terraform-newrelic-init.sh: Permission denied Can someone suggest on this? I am blocked with this. Where can I set permissions to read shell script?
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emai
[JIRA] (JENKINS-41418) Permission denied while accessing workspace
Title: Message Title ASHOK MOHANTY commented on JENKINS-41418 Re: Permission denied while accessing workspace I am getting same permission issue (but its in-frequent) when using different user with uid:1000. Will it help by changing to uid:1 !! I have Jenkins - 2.121.3 and Kubernetes Plugin - 1.12.7 . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178200.1485341884000.6767.1562763000662%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41418) Permission denied while accessing workspace
Title: Message Title Manjunath Kumatagi commented on JENKINS-41418 Re: Permission denied while accessing workspace After trying with all latest - kubernetes, jenkins plugin I'm not seeing this issue anymore. Will report a new issue or reopen this if I hit this issue again, -Thanks. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41418) Permission denied while accessing workspace
Title: Message Title Manjunath Kumatagi closed an issue as Cannot Reproduce Jenkins / JENKINS-41418 Permission denied while accessing workspace Change By: Manjunath Kumatagi Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41418) Permission denied while accessing workspace
Title: Message Title Carlos Sanchez commented on JENKINS-41418 Re: Permission denied while accessing workspace What version of kubernetes are you using? The only reason I can think this would fail is if containers were using different permissions, because they are all accessing the same emptyVolume Can you try exec'ing into the containers and list the permissions in /home/jenkins/workspace and subdirs and possibly trying to write a file in there from the 3 containers to see if it works or fails ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41418) Permission denied while accessing workspace
Title: Message Title
Manjunath Kumatagi edited a comment on JENKINS-41418
Re: Permission denied while accessing workspace
Removed the secret volume and ran the job, hitting with the problem mentioned in the description, "Build a Maven project" stage is failing. Here is the complete build console output:{code:java}Started by user admin > git rev-parse --is-inside-work-tree # timeout=10Setting origin to g...@github.ibm.com:mkumatag/test-kube-pipeline.git > git config remote.origin.url g...@github.ibm.com:mkumatag/test-kube-pipeline.git # timeout=10Fetching origin...Fetching upstream changes from origin > git --version # timeout=10using GIT_SSH to set credentials > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*Seen branch in repository origin/masterSeen 1 remote branch > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url g...@github.ibm.com:mkumatag/test-kube-pipeline.git # timeout=10Fetching upstream changes from g...@github.ibm.com:mkumatag/test-kube-pipeline.git > git --version # timeout=10using GIT_SSH to set credentials > git fetch --tags --progress g...@github.ibm.com:mkumatag/test-kube-pipeline.git +refs/heads/*:refs/remotes/origin/*Checking out Revision 916212bda350d9ea81c1419c2501f5177e396a8b (master) > git config core.sparsecheckout # timeout=10 > git checkout -f 916212bda350d9ea81c1419c2501f5177e396a8b > git rev-list 916212bda350d9ea81c1419c2501f5177e396a8b # timeout=10[Pipeline] podTemplate[Pipeline] {[Pipeline] nodeRunning on kubernetes-3f499c55e0fb4feea46c66e78e82ded3-70682873cd6d3 in /home/jenkins/workspace/test-kube-pipeline_master-IUIW3TJVYLQLCZOGWHIM6BOJZ3VXUBKJ2C2L4YNTBE4GL52NRMEA[Pipeline] {[Pipeline] stage (Get a Maven project)Using the ‘stage’ step without a block argument is deprecatedEntering stage Get a Maven projectProceeding[Pipeline] gitCloning the remote Git repositoryCloning repository https://github.com/jenkinsci/kubernetes-plugin.git > git init /home/jenkins/workspace/test-kube-pipeline_master-IUIW3TJVYLQLCZOGWHIM6BOJZ3VXUBKJ2C2L4YNTBE4GL52NRMEA # timeout=10Fetching upstream changes from https://github.com/jenkinsci/kubernetes-plugin.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/jenkinsci/kubernetes-plugin.git +refs/heads/*:refs/remotes/origin/* > git config remote.origin.url https://github.com/jenkinsci/kubernetes-plugin.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/jenkinsci/kubernetes-plugin.git # timeout=10Fetching upstream changes from https://github.com/jenkinsci/kubernetes-plugin.git > git fetch --tags --progress https://github.com/jenkinsci/kubernetes-plugin.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10Checking out Revision 8078e125c4e2241814ce70a129b8fb7ab4abe81a (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 8078e125c4e2241814ce70a129b8fb7ab4abe81a > git branch -a -v --no-abbrev # timeout=10 > git checkout -b master 8078e125c4e2241814ce70a129b8fb7ab4abe81a > git rev-list 8078e125c4e2241814ce70a129b8fb7ab4abe81a # timeout=10[Pipeline] container[Pipeline] {[Pipeline] stage (Build a Maven project)Using the ‘stage’ step without a block argument is deprecatedEntering stage Build a Maven projectProceeding[Pipeline] sh[test-kube-pipeline_master-IUIW3TJVYLQLCZOGWHIM6BOJZ3VXUBKJ2C2L4YNTBE4GL52NRMEA] Running shell scriptExecuting shell script inside container [maven] of pod [kube
[JIRA] (JENKINS-41418) Permission denied while accessing workspace
Title: Message Title
Manjunath Kumatagi commented on JENKINS-41418
Re: Permission denied while accessing workspace
Removed the secret volume and ran the job, hitting with the problem mentioned in the description, "Build a Maven project" stage is failing. Here is the complete build console output:
Started by user admin
> git rev-parse --is-inside-work-tree # timeout=10
Setting origin to g...@github.ibm.com:mkumatag/test-kube-pipeline.git
> git config remote.origin.url g...@github.ibm.com:mkumatag/test-kube-pipeline.git # timeout=10
Fetching origin...
Fetching upstream changes from origin
> git --version # timeout=10
using GIT_SSH to set credentials
> git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/*
Seen branch in repository origin/master
Seen 1 remote branch
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url g...@github.ibm.com:mkumatag/test-kube-pipeline.git # timeout=10
Fetching upstream changes from g...@github.ibm.com:mkumatag/test-kube-pipeline.git
> git --version # timeout=10
using GIT_SSH to set credentials
> git fetch --tags --progress g...@github.ibm.com:mkumatag/test-kube-pipeline.git +refs/heads/*:refs/remotes/origin/*
Checking out Revision 916212bda350d9ea81c1419c2501f5177e396a8b (master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 916212bda350d9ea81c1419c2501f5177e396a8b
> git rev-list 916212bda350d9ea81c1419c2501f5177e396a8b # timeout=10
[Pipeline] podTemplate
[Pipeline] {
[Pipeline] node
Running on kubernetes-3f499c55e0fb4feea46c66e78e82ded3-70682873cd6d3 in /home/jenkins/workspace/test-kube-pipeline_master-IUIW3TJVYLQLCZOGWHIM6BOJZ3VXUBKJ2C2L4YNTBE4GL52NRMEA
[Pipeline] {
[Pipeline] stage (Get a Maven project)
Using the ‘stage’ step without a block argument is deprecated
Entering stage Get a Maven project
Proceeding
[Pipeline] git
Cloning the remote Git repository
Cloning repository https://github.com/jenkinsci/kubernetes-plugin.git
> git init /home/jenkins/workspace/test-kube-pipeline_master-IUIW3TJVYLQLCZOGWHIM6BOJZ3VXUBKJ2C2L4YNTBE4GL52NRMEA # timeout=10
Fetching upstream changes from https://github.com/jenkinsci/kubernetes-plugin.git
> git --version # timeout=10
> git fetch --tags --progress https://github.com/jenkinsci/kubernetes-plugin.git +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url https://github.com/jenkinsci/kubernetes-plugin.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url https://github.com/jenkinsci/kubernetes-plugin.git # timeout=10
Fetching upstream changes from https://github.com/jenkinsci/kubernetes-plugin.git
> git fetch --tags --progress https://github.com/jenkinsci/kubernetes-plugin.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 8078e125c4e2241814ce70a129b8fb7ab4abe81a (refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 8078e125c4e2241814ce70a129b8fb7ab4abe81a
> git branch -a -v --no-abbrev # timeout=10
> git checkout -b master 8078e125c4e2241814ce70a129b8fb7ab4abe81a
> git rev-list 8078e125c4e2241814ce70a129b8fb7ab4abe81a # timeout=10
[Pipeline] container
[Pipeline] {
[Pipeline] stage (Build a Maven project)
Using the ‘stage’ step without a block argument is deprecat
[JIRA] (JENKINS-41418) Permission denied while accessing workspace
Title: Message Title Carlos Sanchez commented on JENKINS-41418 Re: Permission denied while accessing workspace I have removed the shared-secrets volume from the example, as it won't work out of the bat. You can see the error in your "describe" Warning FailedMount MountVolume.SetUp failed for volume "kubernetes.io/secret/80020c1e-e45c-11e6-9dc3-005056aa2e0b-volume-0" (spec.Name: "volume-0") pod "80020c1e-e45c-11e6-9dc3-005056aa2e0b" (UID: "80020c1e-e45c-11e6-9dc3-005056aa2e0b") with: secrets "shared-secrets" not found Now, if you describe the pods created in your pipeline, do you get error messages in the events section ? Also check kubectl logs pods/(your pod name) jnlp for errors Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41418) Permission denied while accessing workspace
Title: Message Title
Sergey Kulanov commented on JENKINS-41418
Re: Permission denied while accessing workspace
Actually I have the same issue, but it's not 100% reproducible, `waiting to start slave`, that's why I asked your to check the example. Ok so, please try to define jnlp container explicitly:
containerTemplate(
name: 'jnlp',
image: jnlpSlaveImg,
args: '${computer.jnlpmac} ${computer.name}'
)
where jnlpSlaveImg can by upstream jenkinsci/jnlp-slave:2.62-alpine or any other which you customized
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41418) Permission denied while accessing workspace
Title: Message Title Manjunath Kumatagi commented on JENKINS-41418 Re: Permission denied while accessing workspace I copy pasted exact code from above git repo and tried running it,.. Jos is waiting for slave to be up and running to run the job but slave never came up and here what I find in the kubernetes: [root@ kubernetes]# ./cluster/kubectl.sh get pods NAMEREADY STATUS RESTARTS AGE kubernetes-68ce0b016db741cc9bc7f89b961e3bbd-57f30d1779ab9 0/3 ContainerCreating 0 5m [root@ kubernetes]# ./cluster/kubectl.sh describe pod kubernetes-68ce0b016db741cc9bc7f89b961e3bbd-57f30d1779ab9 Name: kubernetes-68ce0b016db741cc9bc7f89b961e3bbd-57f30d1779ab9 Namespace: default Node: 127.0.0.1/127.0.0.1 Start Time: Fri, 27 Jan 2017 01:47:41 -0500 Labels: jenkins=slave jenkins/mypod=true Status: Pending IP: Controllers: Containers: maven: Container ID: Image: maven:3.3.9-jdk-8-alpine Image ID: Port: Command: cat State: Waiting Reason: ContainerCreating Ready: False Restart Count: 0 Volume Mounts: /etc/shared-secrets from volume-0 (rw) /home/jenkins from workspace-volume (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-jqq8v (ro) Environment Variables from: Environment Variables: JENKINS_SECRET: 0c574b20fd8c968fbc2671d550c454c8c15e9cbb4cb810055c9dae547ac428a5 JENKINS_NAME: kubernetes-68ce0b016db741cc9bc7f89b961e3bbd-57f30d1779ab9 JENKINS_LOCATION_URL: http://:8080/ JENKINS_URL: http://:8080 JENKINS_JNLP_URL: http://:8080/computer/kubernetes-68ce0b016db741cc9bc7f89b961e3bbd-57f30d1779ab9/slave-agent.jnlp HOME: /home/jenkins golang: Container ID: Image: golang:1.6.3-alpine Image ID: Port: Command: cat State: Waiting Reason: ContainerCreating Ready: False Restart Count: 0 Volume Mounts: /etc/shared-secrets from volume-0 (rw) /home/jenkins from workspace-volume (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-jqq8v (ro) Environment Variables from: Environment Variables: JENKINS_SECRET: 0c574b20fd8c968fbc2671d550c454c8c15e9cbb4cb810055c9dae547ac428a5 JENKINS_NAME: kubernetes-68ce0b016db741cc9bc7f89b961e3bbd-57f30d1779ab9 JENKINS_LOCATION_URL: http://:8080/ JENKINS_URL: http://:8080 JENKINS_JNLP_URL: http://:8080/computer/kubernetes-68ce0b016db741cc9bc7f89b961e3bbd-57f30d1779ab9/slave-agent.jnlp HOME: /home/jenkins jnlp: Container ID: Image: jenkinsci/jnlp-slave:alpine Image ID: Port: Args: 0c574b20fd8c968fbc2671d550c454c8c15e9cbb4cb810055c9dae547ac428a5 kubernetes-68ce0b016db741cc9bc7f89b961e3bbd-57f30d1779ab9 State: Waiting Reason: ContainerCreating Ready: False Restart Count: 0 Volume Mounts: /etc/shared-secrets from volume-0 (rw) /home/jenkins from workspace-volume (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-jqq8v (ro) Environment Variables from: Environment Variables: JENKINS_SECRET: 0c574b20fd8c968fbc2671d550c454c8c15e9cbb4cb810055c9dae547ac428a5 JENKINS_NAME: kubernetes-68ce0b016db741cc9bc7f89b961e3bbd-57f30d1779ab9 JENKINS_LOCATION_URL: http://:8080/ JENKINS_URL: http://:8080 JENKINS_JNLP_URL: http://:8080/computer/
[JIRA] (JENKINS-41418) Permission denied while accessing workspace
Title: Message Title Sergey Kulanov commented on JENKINS-41418 Re: Permission denied while accessing workspace please try to copy/paste the exact code from example https://github.com/jenkinsci/kubernetes-plugin#pipeline-support and paste the result here Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41418) Permission denied while accessing workspace
Title: Message Title
Manjunath Kumatagi commented on JENKINS-41418
Re: Permission denied while accessing workspace
Here is the pod in yaml format which got created while running this job:
apiVersion: v1
kind: Pod
metadata:
creationTimestamp: 2017-01-25T07:13:22Z
labels:
jenkins: slave
jenkins/mypod: "true"
name: kubernetes-634383bd02e4408a9ad879376fa358c7-4e36e7bfa07c9
namespace: default
resourceVersion: "860"
selfLink: /api/v1/namespaces/default/pods/kubernetes-634383bd02e4408a9ad879376fa358c7-4e36e7bfa07c9
uid: c19b9100-e2cd-11e6-b29b-005056aa2e0b
spec:
containers:
- command:
- cat
env:
- name: JENKINS_SECRET
value: 367fe11e3c73e1032ec45faaeea7f06526a32d182b87d3234fd8374e9893ec31
- name: JENKINS_NAME
value: kubernetes-634383bd02e4408a9ad879376fa358c7-4e36e7bfa07c9
- name: JENKINS_LOCATION_URL
value: http://jenkins-master:8080/
- name: JENKINS_URL
value: http://jenkins-master:8080
- name: JENKINS_JNLP_URL
value: http://jenkins-master:8080/computer/kubernetes-634383bd02e4408a9ad879376fa358c7-4e36e7bfa07c9/slave-agent.jnlp
- name: HOME
value: /home/jenkins
image: maven:3.3.9-jdk-8-alpine
imagePullPolicy: IfNotPresent
name: maven
resources: {}
securityContext:
privileged: false
terminationMessagePath: /dev/termination-log
tty: true
volumeMounts:
- mountPath: /var/run/docker.sock
name: volume-0
- mountPath: /home/jenkins
name: workspace-volume
- mountPath: /var/run/secrets/kubernetes.io/serviceaccount
name: default-token-q4pkd
readOnly: true
workingDir: /home/jenkins
- command:
- cat
env:
- name: JENKINS_SECRET
value: 367fe11e3c73e1032ec45faaeea7f06526a32d182b87d3234fd8374e9893ec31
- name: JENKINS_NAME
value: kubernetes-634383bd02e4408a9ad879376fa358c7-4e36e7bfa07c9
- name: JENKINS_LOCATION_URL
value: http://jenkins-master:8080/
- name: JENKINS_URL
value: http://jenkins-master:8080
- name: JENKINS_JNLP_URL
value: http://jenkins-master:8080/computer/kubernetes-634383bd02e4408a9ad879376fa358c7-4e36e7bfa07c9/slave-agent.jnlp
- name: HOME
value: /home/jenkins
image: golang:1.6.3-alpine
imagePullPolicy: IfNotPresent
name: golang
resources: {}
securityContext:
privileged: false
terminationMessagePath: /dev/termination-log
tty: true
volumeMounts:
- mountPath: /var/run/docker.sock
name: volume-0
- mountPath: /home/jenkins
name: workspace-volume
- mountPath: /var/run/secrets/kubernetes.io/serviceaccount
name: default-token-q4pkd
readOnly: true
workingDir: /home/jenkins
- args:
- 367fe11e3c73e1032ec45faaeea7f06526a32d182b87d3234fd8374e9893ec31
- kubernetes-634383bd02e4408a9ad879376fa358c7-4e36e7bfa07c9
env:
- name: JENKINS_SECRET
value: 367fe11e3c73e1032ec45faaeea7f06526a32d182b87d3234fd8374e9893ec31
- name: JENKINS_NAME
value: kubernetes-634383bd02e4408a9ad879376fa358c7-4e36e7bfa07c9
- name: JENKINS_LOCATION_URL
value: http://jenkins-master:8080/
- name: JENKINS_URL
value: http://jenkins-master:8080
- name: JENKINS_JNLP_URL
value: http://jenkins-master:8080/computer/kubernetes-634383bd02e4408a9ad879376fa358c7-4e36e7bfa07c9/slave-agent.jnlp
- name: HOME
value: /home/jenkins
image: jenkinsci/jnlp-slave:alpine
imagePullPolicy: IfNotPresent
name: jnlp
res
[JIRA] (JENKINS-41418) Permission denied while accessing workspace
Title: Message Title
Manjunath Kumatagi created an issue
Jenkins / JENKINS-41418
Permission denied while accessing workspace
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2017/Jan/25 10:58 AM
Priority:
Major
Reporter:
Manjunath Kumatagi
I've added kubernetes cloud in system config and created git project with following Jenkinsfile and trying to run the job and hitting with following permission issues.
podTemplate(label: 'mypod', containers: [
containerTemplate(name: 'maven', image: 'maven:3.3.9-jdk-8-alpine', ttyEnabled: true, command: 'cat'),
containerTemplate(name: 'golang', image: 'golang:1.6.3-alpine', ttyEnabled: true, command: 'cat')
],
volumes: [hostPathVolume(mountPath: "/var/run/docker.sock", hostPath: "/var/run/docker.sock")]) {
node ('mypod') {
stage 'Get a Maven project'
sh """
cat /etc/resolv.conf
route
ip addr show
"""
git 'https://github.com/jenkinsci/kubernetes-plugin.git'
container('maven') {
stage 'Build a Maven project'
sh 'mvn clean install'
}
stage 'Get a Golang project'
git url: 'https://github.com/hashicorp/terraform.git'
container('golang') {
stage 'Build a Go project'
sh """
mkdir -p /go/src/github.com/hashicorp
ln -s `pwd` /go/src/github.com/hashicorp/terraform
cd /go/src/github.com/hashicorp/terraform && make core-dev
"""
}
}
}
Error:
