ERROR: failed to solve: process "/bin/sh -c chmod +x /entrypoint.sh" did not complete successfully: exit code: 1 #104

Badr-Tarek · 2024-04-16T16:01:38Z

0.165 chmod: /entrypoint.sh: Operation not permitted

richard-green · 2024-04-16T16:02:53Z

Also getting this:

#8 0.184 chmod: /entrypoint.sh: Operation not permitted
#8 ERROR: process "/bin/sh -c chmod +x /entrypoint.sh" did not complete successfully: exit code: 1

wooseung-sim · 2024-04-16T16:06:48Z

Same here

cedric-appdirect · 2024-04-16T16:07:08Z

I am also seeing this since this morning. It was working fine 16 hours ago. It is a bit concerning as there was no new release of this action.

mcarrillowz · 2024-04-16T16:07:43Z

Same, the Docker image was updated 26 minutes ago

dchekirda · 2024-04-16T16:08:11Z

See this problem as well. Worked about few hours before without issues.

paulomcnally · 2024-04-16T16:14:09Z

/usr/bin/docker build -t a6b84c:b5f9e2265622469fa398122ab4656888 -f "/home/runner/work/_actions/sonarsource/sonarqube-scan-action/master/Dockerfile" "/home/runner/work/_actions/sonarsource/sonarqube-scan-action/master"
  #0 building with "default" instance using docker driver
  
  #1 [internal] load .dockerignore
  #1 transferring context: 2B done
  #1 DONE 0.0s
  
  #2 [internal] load build definition from Dockerfile
  #2 transferring dockerfile: 713B done
  #2 DONE 0.0s
  
  #3 [internal] load metadata for docker.io/sonarsource/sonar-scanner-cli:5.0.1
  #3 ...
  
  #4 [auth] sonarsource/sonar-scanner-cli:pull token for registry-1.docker.io
  #4 DONE 0.0s
  
  #3 [internal] load metadata for docker.io/sonarsource/sonar-scanner-cli:5.0.1
  #3 DONE 0.7s
  
  #5 [internal] load build context
  #5 transferring context: 1.50kB done
  #5 DONE 0.0s
  
  #6 [1/5] FROM docker.io/sonarsource/sonar-scanner-cli:5.0.1@sha256:c137f8c67272971c001aad747dce830d81d62dce25acd0e4b8ae7290b225657c
  #6 resolve docker.io/sonarsource/sonar-scanner-cli:5.0.1@sha256:c137f8c67272971c001aad747dce830d81d62dce25acd0e4b8ae7290b225657c done
  #6 extracting sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1 done
  #6 sha256:d365f01690bdede439d1a63dfae47b45094a5cb56793a9364b013d3015011dc8 4.82kB / 4.82kB done
  #6 sha256:4f4fb700ef54461cfa02571ae0db9a0dc1e0cdb5577484a6d75e68dc38e8acc1 32B / 32B 0.1s done
  #6 sha256:77aac2b8cbb6a7dbf8c9fa2e73a04c9d77e9517f5e9eb661997a1000a042c4cc 0B / 99.47MB 0.1s
  #6 sha256:6180196e68a7518ea1de1b0734c3b28e4e0d17e623263e13f79978c48c440f09 0B / 736B 0.1s
  #6 sha256:c137f8c67272971c001aad747dce830d81d62dce25acd0e4b8ae7290b225657c 1.36kB / 1.36kB done
  #6 sha256:77aac2b8cbb6a7dbf8c9fa2e73a04c9d77e9517f5e9eb661997a1000a042c4cc 9.44MB / 99.47MB 0.3s
  #6 sha256:6180196e68a7518ea1de1b0734c3b28e4e0d17e623263e13f79978c48c440f09 736B / 736B 0.2s done
  #6 sha256:77aac2b8cbb6a7dbf8c9fa2e73a04c9d77e9517f5e9eb661997a1000a042c4cc 19.92MB / 99.47MB 0.4s
  #6 sha256:77aac2b8cbb6a7dbf8c9fa2e73a04c9d77e9517f5e9eb661997a1000a042c4cc 27.26MB / 99.47MB 0.5s
  #6 sha256:77aac2b8cbb6a7dbf8c9fa2e73a04c9d77e9517f5e9eb661997a1000a042c4cc 33.55MB / 99.47MB 0.6s
  #6 sha256:77aac2b8cbb6a7dbf8c9fa2e73a04c9d77e9517f5e9eb661997a1000a042c4cc 49.28MB / 99.47MB 0.8s
  #6 sha256:77aac2b8cbb6a7dbf8c9fa2e73a04c9d77e9517f5e9eb661997a1000a042c4cc 59.77MB / 99.47MB 0.9s
  #6 sha256:77aac2b8cbb6a7dbf8c9fa2e73a04c9d77e9517f5e9eb661997a1000a042c4cc 66.06MB / 99.47MB 1.0s
  #6 sha256:77aac2b8cbb6a7dbf8c9fa2e73a04c9d77e9517f5e9eb661997a1000a042c4cc 78.64MB / 99.47MB 1.1s
  #6 sha256:77aac2b8cbb6a7dbf8c9fa2e73a04c9d77e9517f5e9eb661997a1000a042c4cc 99.47MB / 99.47MB 1.3s
  #6 sha256:77aac2b8cbb6a7dbf8c9fa2e73a04c9d77e9517f5e9eb661997a1000a042c4cc 99.47MB / 99.47MB 1.5s done
  #6 extracting sha256:77aac2b8cbb6a7dbf8c9fa2e73a04c9d77e9517f5e9eb661997a1000a042c4cc
  #6 extracting sha256:77aac2b8cbb6a7dbf8c9fa2e73a04c9d77e9517f5e9eb661997a1000a042c4cc 2.6s done
  #6 extracting sha256:6180196e68a7518ea1de1b0734c3b28e4e0d17e623263e13f79978c48c440f09
  #6 extracting sha256:6180196e68a7518ea1de1b0734c3b28e4e0d17e623263e13f79978c48c440f09 done
  #6 DONE 6.7s
  
  ------
  Dockerfile:14
  --------------------
    12 |     
    13 |     COPY entrypoint.sh /entrypoint.sh
    14 | >>> RUN chmod +x /entrypoint.sh
    15 |     COPY cleanup.sh /cleanup.sh
    16 |     RUN chmod +x /cleanup.sh
  --------------------
  ERROR: failed to solve: process "/bin/sh -c chmod +x /entrypoint.sh" did not complete successfully: exit code: 1
  Warning: Docker build failed with exit code 1, back off 9.551 seconds before retry.
  /usr/bin/docker build -t a6b84c:b5f9e2265622469fa398122ab4656888 -f "/home/runner/work/_actions/sonarsource/sonarqube-scan-action/master/Dockerfile" "/home/runner/work/_actions/sonarsource/sonarqube-scan-action/master"
  #0 building with "default" instance using docker driver
  
  #1 [internal] load .dockerignore
  #1 transferring context: 2B done
  #1 DONE 0.0s
  
  #2 [internal] load build definition from Dockerfile
  #2 transferring dockerfile: 713B done
  #2 DONE 0.0s
  
  #3 [internal] load metadata for docker.io/sonarsource/sonar-scanner-cli:5.0.1
  #3 DONE 0.2s
  
  #4 [1/5] FROM docker.io/sonarsource/sonar-scanner-cli:5.0.1@sha256:c137f8c67272971c001aad747dce830d81d62dce25acd0e4b8ae7290b225657c
  #4 DONE 0.0s
  
  #5 [internal] load build context
  #5 transferring context: 65B done
  #5 DONE 0.0s
  
  #6 [2/5] COPY entrypoint.sh /entrypoint.sh
  #6 CACHED
  
  #7 [3/5] RUN chmod +x /entrypoint.sh
  #7 0.174 chmod: /entrypoint.sh: Operation not permitted
  #7 ERROR: process "/bin/sh -c chmod +x /entrypoint.sh" did not complete successfully: exit code: 1
  ------
   > [3/5] RUN chmod +x /entrypoint.sh:
  0.174 chmod: /entrypoint.sh: Operation not permitted
  ------
  Dockerfile:14
  --------------------
    12 |     
    13 |     COPY entrypoint.sh /entrypoint.sh
    14 | >>> RUN chmod +x /entrypoint.sh
    15 |     COPY cleanup.sh /cleanup.sh
    16 |     RUN chmod +x /cleanup.sh
  --------------------
  ERROR: failed to solve: process "/bin/sh -c chmod +x /entrypoint.sh" did not complete successfully: exit code: 1
Error: Docker build failed with exit code 1

cedric-appdirect · 2024-04-16T16:17:39Z

As pointed above a new image has been pushed and override the 9 months old 5.0.1 release with a new release with the same docker tag. This is now pulled by this github action. I think the fix should be in the sonar-scanner-cli-docker. It should not ever overwrite a release.

kevin-kraus · 2024-04-16T16:23:44Z

Same also happening for https://github.com/SonarSource/sonarcloud-github-action.

Issue in Parent Image Repo: SonarSource/sonar-scanner-cli-docker#224

damanrique · 2024-04-16T16:24:04Z

same error with docker image

guerlielton-nunes · 2024-04-16T16:40:14Z

to workaround I fixed my action in this version sonarsource/sonarqube-scan-action@v1.2.0 this version user cli-4.8

wwsean08 · 2024-04-16T16:55:50Z

A temp fix is to point at commit sha 465a122c48499009db491f0847ecee9cf9f20b50 which is in my fork that I generated to unblock the reusable workflows at my job, this forces it to use the previously working container

ivan-poznyak-mint · 2024-04-16T16:59:30Z

same issue

drilonibrahimi · 2024-04-16T17:03:54Z

to workaround I fixed my action in this version sonarsource/sonarqube-scan-action@v1.2.0 this version user cli-4.8

Can confirm this worked on my use case, thx @guerlielton-nunes

damanrique · 2024-04-16T17:04:11Z

v1.2.0

it works as a workaround. thanks

rathpc · 2024-04-16T17:10:34Z

also have this problem but down-pinning to 1.2.0 is not an option. anyone from sonar willing to chime in on this issue?

@claire-villard-sonarsource @matteo-mara-sonarsource

dsayling · 2024-04-16T17:14:00Z

Interesting that pinning the image in the other action is what's being done...

SonarSource/sonarcloud-github-action#67

theibrarkhan · 2024-04-16T17:24:27Z

See this problem as well. Worked about few hours before without issues.

ronaldofysight · 2024-04-16T17:25:12Z

Same issue.

  #8 [3/5] RUN chmod +x /entrypoint.sh
  #8 0.178 chmod: /entrypoint.sh: Operation not permitted
  #8 ERROR: process "/bin/sh -c chmod +x /entrypoint.sh" did not complete successfully: exit code: 1

Ifletcher668 · 2024-04-16T17:25:26Z

Same issue here

mattriordan1uphealth · 2024-04-16T17:34:05Z

A temp fix is to point at commit sha 465a122c48499009db491f0847ecee9cf9f20b50 which is in my fork that I generated to unblock the reusable workflows at my job, this forces it to use the previously working container

This sha worked for us while v1.2.0 did not.

arrmansa · 2024-04-16T17:35:38Z

I have the same issue with the rick and morty hash
c137f8c67272971c001aad747dce830d81d62dce25acd0e4b8ae7290b225657c
the previous one worked correctly
494ecc3b5b1ee1625bd377b3905c4284e4f0cc155cff397805a244dee1c7d575

psadi · 2024-04-16T17:40:55Z

Facing the same error

#9 [4/6] RUN chmod +x /entrypoint.sh
  #9 0.176 chmod: /entrypoint.sh: Operation not permitted
  #9 ERROR: process "/bin/sh -c chmod +x /entrypoint.sh" did not complete successfully: exit code: 1
  ------
   > [4/6] RUN chmod +x /entrypoint.sh:
  0.176 chmod: /entrypoint.sh: Operation not permitted
  ------
  Dockerfile:24
  --------------------
    22 |     # Prepare entrypoint
    23 |     COPY entrypoint.sh /entrypoint.sh
    24 | >>> RUN chmod +x /entrypoint.sh
    25 |     COPY cleanup.sh /cleanup.sh
    26 |     RUN chmod +x /cleanup.sh
  --------------------
  ERROR: failed to solve: process "/bin/sh -c chmod +x /entrypoint.sh" did not complete successfully: exit code: 1
  Warning: Docker build failed with exit code 1, back off 8.997 seconds before retry.
  /usr/bin/docker build -t f3e1f2:00e283dde[55](https://github.com/psadi/bbcli/actions/runs/8709992075/job/23890878538#step:2:55)84fceab9582a840bb65be -f "/home/runner/work/_actions/sonarsource/sonarcloud-github-action/master/Dockerfile" "/home/runner/work/_actions/sonarsource/sonarcloud-github-action/master"

any suggestions ?

gfoligna-nyshex · 2024-04-16T17:43:32Z

Watching this helps. It is also live with changes.

Interesting that pinning the image in the other action is what's being done...

SonarSource/sonarcloud-github-action#67

sveinse · 2024-04-16T17:51:20Z

Same here. 2 hours ago it worked and then it stopped. Something changed either with this action or in the github environment very recently.

jupitercl · 2024-04-16T18:24:50Z

Same here

mviegasdeb · 2024-04-16T18:26:54Z

SAME BRO

Iherreradeb · 2024-04-16T18:28:16Z

any news ? roswell need this to funtion!

andrevandal · 2024-04-16T18:31:35Z

same here

fabiocruzcoelho · 2024-04-16T18:37:24Z

same here

ademolaarigbabuwo-8451 · 2024-04-16T18:38:00Z

same here

elmijo · 2024-04-16T18:38:19Z

same here

lsadam0 · 2024-04-16T18:43:08Z

I just want to be sure, is the issue also happening to everyone else here?

kumar08401 · 2024-04-16T18:43:24Z

Hi Team,

having issue with this plugin, geeting below error

Dockerfile:24

22 |     # Prepare entrypoint
23 |     COPY entrypoint.sh /entrypoint.sh
24 | >>> RUN chmod +x /entrypoint.sh
25 |     COPY cleanup.sh /cleanup.sh
26 |     RUN chmod +x /cleanup.sh

andrevandal · 2024-04-16T18:45:22Z

guys, G Ann Campbell said:

There is currently an outage related to the SonarScanner CLI Docker image that affects the GitHub actions for both SonarQube and SonarCloud.

We are aware of the problem and are working to solve it.

In the meantime, you can work around this

For SonarQube
Pin to version 2.0 of the scan action to use the older (working) version of the scan action

We apologize for the inconvenience.

Ann & the Sonar team

https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548

LuccasSartori · 2024-04-16T18:45:35Z

to workaround I fixed my action in this version sonarsource/sonarqube-scan-action@v1.2.0 this version user cli-4.8

This worked for me, tks.

elmijo · 2024-04-16T18:49:25Z

I just want to be sure, is the issue also happening to everyone else here?

yep, it's the same issue:

  #7 [3/5] RUN chmod +x /entrypoint.sh
  #7 0.178 chmod: /entrypoint.sh: Operation not permitted
  #7 ERROR: process "/bin/sh -c chmod +x /entrypoint.sh" did not complete successfully: exit code: 1
  ------
   > [3/5] RUN chmod +x /entrypoint.sh:
  0.178 chmod: /entrypoint.sh: Operation not permitted
  ------
  Dockerfile:14
  --------------------
    12 |     
    13 |     COPY entrypoint.sh /entrypoint.sh
    14 | >>> RUN chmod +x /entrypoint.sh
    15 |     COPY cleanup.sh /cleanup.sh
    16 |     RUN chmod +x /cleanup.sh
  --------------------
  ERROR: failed to solve: process "/bin/sh -c chmod +x /entrypoint.sh" did not complete successfully: exit code: 1

dsayling · 2024-04-16T18:51:04Z

guys, G Ann Campbell said:

There is currently an outage related to the SonarScanner CLI Docker image that affects the GitHub actions for both SonarQube and SonarCloud.
We are aware of the problem and are working to solve it.
In the meantime, you can work around this
For SonarQube
Pin to version 2.0 of the scan action to use the older (working) version of the scan action
We apologize for the inconvenience.
Ann & the Sonar team

https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548

an "outage"??

This is not an outage, this was a bad release that overwrote an existing docker tag that impacted downstream dependencies.

vyas-n · 2024-04-16T18:56:12Z

@dsayling For GitHub Actions, this is the equivalent of an outage.

this was a bad release that overwrote an existing docker tag that impacted downstream dependencies.

Similar to if we're doing an HTTP call to a web server and that web server is down. Our HTTP call is not an outage, it's just affected by being a downstream dependency of a web server.

svaranasi-corporate · 2024-04-16T18:57:53Z

guys, G Ann Campbell said:

There is currently an outage related to the SonarScanner CLI Docker image that affects the GitHub actions for both SonarQube and SonarCloud.
We are aware of the problem and are working to solve it.
In the meantime, you can work around this
For SonarQube
Pin to version 2.0 of the scan action to use the older (working) version of the scan action
We apologize for the inconvenience.
Ann & the Sonar team

https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548

Doesn't work for me. I get the same error with v2.0 as well as v2.0.0.. yes they have 2 tags!

wooseung-sim · 2024-04-16T19:08:48Z

guys, G Ann Campbell said:

There is currently an outage related to the SonarScanner CLI Docker image that affects the GitHub actions for both SonarQube and SonarCloud.
We are aware of the problem and are working to solve it.
In the meantime, you can work around this
For SonarQube
Pin to version 2.0 of the scan action to use the older (working) version of the scan action
We apologize for the inconvenience.
Ann & the Sonar team

https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548

Doesn't work for me. I get the same error with v2.0 as well as v2.0.0.. yes they have 2 tags!

Seems like wrong instructions. Per commit history of the action, working version should be v1.2.0. which uses scan container image 4.8

ganncamp · 2024-04-16T19:35:31Z

https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/29

dsayling · 2024-04-16T19:52:47Z

Confirmed - issue is resolved (at least using sonarqube-scan-action@master) Other versions should probably be just fine again as well

matheusalxds · 2024-04-16T19:54:50Z

Confirmed - issue is resolved (at least using sonarqube-scan-action@master) Other versions should probably be just fine again as well

Yeah! It's everything working fine! :D

nstankov-bg · 2024-04-17T13:38:44Z

Issue is also happening here: SonarSource/sonarqube-quality-gate-action#53

cedric-appdirect mentioned this issue Apr 16, 2024

Incorrect docker image being pushed SonarSource/sonar-scanner-cli-docker#223

Closed

kevin-kraus mentioned this issue Apr 16, 2024

Error in Docker Build: chmod: /entrypoint.sh: Operation not permitted SonarSource/sonar-scanner-cli-docker#224

Closed

2 tasks

bonddim mentioned this issue Apr 16, 2024

Fix setting file permissions #105

Closed

Badr-Tarek closed this as completed Apr 16, 2024

nstankov-bg mentioned this issue Apr 17, 2024

ERROR: failed to solve: process "/bin/sh -c chmod +x /entrypoint.sh" did not complete successfully: exit code: 1 SonarSource/sonarqube-quality-gate-action#53

Open

ERROR: failed to solve: process "/bin/sh -c chmod +x /entrypoint.sh" did not complete successfully: exit code: 1 #104

ERROR: failed to solve: process "/bin/sh -c chmod +x /entrypoint.sh" did not complete successfully: exit code: 1 #104

Comments

Badr-Tarek commented Apr 16, 2024 • edited

richard-green commented Apr 16, 2024

wooseung-sim commented Apr 16, 2024

cedric-appdirect commented Apr 16, 2024

mcarrillowz commented Apr 16, 2024

dchekirda commented Apr 16, 2024

paulomcnally commented Apr 16, 2024

cedric-appdirect commented Apr 16, 2024

kevin-kraus commented Apr 16, 2024

damanrique commented Apr 16, 2024

guerlielton-nunes commented Apr 16, 2024

wwsean08 commented Apr 16, 2024

ivan-poznyak-mint commented Apr 16, 2024

drilonibrahimi commented Apr 16, 2024

damanrique commented Apr 16, 2024

rathpc commented Apr 16, 2024

dsayling commented Apr 16, 2024

theibrarkhan commented Apr 16, 2024

ronaldofysight commented Apr 16, 2024

Ifletcher668 commented Apr 16, 2024

mattriordan1uphealth commented Apr 16, 2024

arrmansa commented Apr 16, 2024

psadi commented Apr 16, 2024

gfoligna-nyshex commented Apr 16, 2024

sveinse commented Apr 16, 2024

jupitercl commented Apr 16, 2024

mviegasdeb commented Apr 16, 2024

Iherreradeb commented Apr 16, 2024

andrevandal commented Apr 16, 2024

fabiocruzcoelho commented Apr 16, 2024

ademolaarigbabuwo-8451 commented Apr 16, 2024

elmijo commented Apr 16, 2024

lsadam0 commented Apr 16, 2024

kumar08401 commented Apr 16, 2024

Dockerfile:24

andrevandal commented Apr 16, 2024

LuccasSartori commented Apr 16, 2024

elmijo commented Apr 16, 2024

dsayling commented Apr 16, 2024

vyas-n commented Apr 16, 2024

svaranasi-corporate commented Apr 16, 2024 • edited

wooseung-sim commented Apr 16, 2024 • edited

ganncamp commented Apr 16, 2024

dsayling commented Apr 16, 2024 • edited

matheusalxds commented Apr 16, 2024

nstankov-bg commented Apr 17, 2024

Badr-Tarek commented Apr 16, 2024 •

edited

svaranasi-corporate commented Apr 16, 2024 •

edited

wooseung-sim commented Apr 16, 2024 •

edited

dsayling commented Apr 16, 2024 •

edited