IIUC, you're using a bind mount. You want to avoid it. See https://batmat.net/2018/09/07/how-to-run-and-upgrade-jenkins-using-the-official-docker-image/
Also, I seem to understand you're running your workload on the master node. You want to strongly prefer setting the master with 0 executor, and run builds on agents. Cheers Le ven. 21 sept. 2018 à 09:45, sweeny_here <[email protected]> a écrit : > > 0down voteaccept > > The issue is now resolved and consisted of two parts - > > First off - the EFS mount point directory (/var/jenkins_home) required > permissions of 777, it doesn't need to be a recursive permission. > > The new EFS disk had content migrated from the old Jenkins EFS and this > was also contributing to this issue. The fix was to not transfer any > content from the old EFS to the new EFS via the backup.tar.gz feature. The > new Jenkins is working as expected with npm install. > > Dockerfile pulled from - https://hub.docker.com/r/jenkins/jenkins/ > > On Friday, 21 September 2018 00:31:44 UTC+1, sweeny_here wrote: >> >> Hello there - I've a frustrating issue when "npm install" is executed >> inside a Jenkins Groovy pipeline using the NodeJS plugin, the process hangs >> with the following error - >> >> npm install --ddd ng-cli >> npm info it worked if it ends with ok >> npm verb cli [ >> '/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs893-v2/bin/node', >> npm verb cli >> >> '/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/nodejs893-v2/bin/npm', >> npm verb cli 'install', >> npm verb cli '--ddd', >> npm verb cli 'ng-cli' ] >> npm info using [email protected] >> npm info using [email protected] >> npm verb npm-session e522ad0a36f1c038 >> npm sill install loadCurrentTree >> npm sill install readLocalPackageData >> npm http fetch GET 503 https://registry.npmjs.org/ng-cli 70252ms attempt >> #3 >> npm sill fetchPackageMetaData error for ng-cli@latest 503 Service >> Unavailable: ng-cli@latest >> npm verb stack Error: 503 Service Unavailable: ng-cli@latest >> >> When the command is executed directly on the EC2, the package installs >> without issue as the Jenkins user. >> >> Also when the npm install is executed inside the Jenkins Docker, the >> package installs without issue as the Jenkins user using the same Node >> installation. >> >> The Docker instance is not limited by CPU or RAM. >> >> The setup is Jenkins v2.138.1 running inside a Docker container, which in >> turn is hosted on an EC2 v2018.03. Jenkins home is mounted as an EFS >> volume. The JVM is running on Java v1.8.0_181. NPM is v5.1.1. >> >> Any pointers would be much appreciated. >> > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/e872fc84-7f4c-4378-a17b-f8bdb0dc379e%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/e872fc84-7f4c-4378-a17b-f8bdb0dc379e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS45EfLPxx4Lkcq9CutsWzSWMZ-PARpHQYejMy7_5F1kdQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
