[JIRA] (JENKINS-58657) sh not working inside docker container
Title: Message Title Anatoly Basov commented on JENKINS-58657 Re: sh not working inside docker container I have run into this issue too. In my case the problem was an empty env variable. I have made a PR https://github.com/jenkinsci/docker-workflow-plugin/pull/185 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.200938.1564047916000.9503.1566812880457%40Atlassian.JIRA.
[JIRA] (JENKINS-58657) sh not working inside docker container
Title: Message Title Erik Wegner commented on JENKINS-58657 Re: sh not working inside docker container Update: the directory was created, but for the wrong user. The directory was created by/for user id 1000, but my second container was using id 1. The directory's permissions are set to 0x755. Updating the Dockerfile helped to run the script again. 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.200938.1564047916000.6157.1564732680150%40Atlassian.JIRA.
[JIRA] (JENKINS-58657) sh not working inside docker container
Title: Message Title Erik Wegner commented on JENKINS-58657 Re: sh not working inside docker container This seems somewhat related to https://github.com/jenkinsci/docker/issues/626#issuecomment-508444712 In my scenario, there are two containers on a kubernetes pod, one is the jnlp-slave. The directory /home/jenkins/agent/workspace/@tmp/durable-831063bb exists and is used for steps running inside the jnlp-container. The sh-step running inside the other container tries to access the wrong directory and outputs these messages: sh: 1: cannot create /home/jenkins/agent/workspace/@tmp/durable-6535bde4/jenkins-log.txt: Permission denied sh: 1: cannot create /home/jenkins/agent/workspace/@tmp/durable-6535bde4/jenkins-result.txt.tmp: Permission denied touch: cannot touch '/home/jenkins/agent/workspace/@tmp/durable-6535bde4/jenkins-log.txt': Permission denied mv: cannot stat '/home/jenkins/agent/workspace/@tmp/durable-6535bde4/jenkins-result.txt.tmp': No such file or directory touch: cannot touch '/home/jenkins/agent/workspace/@tmp/durable-6535bde4/jenkins-log.txt': Permission denied 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.200938.1564047916000.5585.1564673640398%40Atlassian.JIRA.
[JIRA] (JENKINS-58657) sh not working inside docker container
Title: Message Title
Oleksandr Zhyhalo created an issue
Jenkins / JENKINS-58657
sh not working inside docker container
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
docker
Created:
2019-07-25 09:45
Priority:
Minor
Reporter:
Oleksandr Zhyhalo
sh command not working wile specifying user to run inside contrainer. Example:
docker.image('node:latest').inside('--user node') {
stage('Pull repository') {
sh 'whoami'
}
In this case checkout and other jenkins functions is working, but not any of sh Process is pending for 5 minutes and then return:
process apparently never started in /var/lib/jenkins/workspace/contrail-ui/contrail-ui-builder@2@tmp/durable-ae2b4ade (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)
Error appears to be with any container.
