# Outage: SonarScanner CLI Docker + SonarQube & SonarCloud GitHub Actions

**URL:** <https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548>\
**Category:** Sonar Updates\
**Tags:** scanner\
**Created:** [April 16, 2024, 6:40pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548 "2024-04-16T18:40:32Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\
**Post date:** [April 16, 2024, 6:40pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/1 "2024-04-16T18:40:32Z")

</div>

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.

We apologize for the inconvenience.

&nbsp;  
Ann & the Sonar team

**UPDATE**

> [@Outage: SonarScanner CLI Docker + SonarQube & SonarCloud GitHub Actions](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/29):
>
> Hi all, We’ve restored a working version of the underlying Scanner CLI Docker image. This should now be fixed for everyone. Sorry, again, for the inconvenience. &nbsp; Ann

---

<div class="post-metadata">

**Author:** ![Alex\_Lo](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/alex_lo/32/56711_2.png) [@Alex\_Lo](https://community.sonarsource.com/u/Alex_Lo)\
**Post date:** [April 16, 2024, 4:18pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/2 "2024-04-16T16:18:38Z")

</div>

we are using sonarsource/sonarcloud-github-action@master

Issue seems to be [sonarcloud-github-action/Dockerfile at master · SonarSource/sonarcloud-github-action · GitHub](https://github.com/SonarSource/sonarcloud-github-action/blob/master/Dockerfile#L24)

[sonarcloud-github-action/Dockerfile at master · SonarSource/sonarcloud-github-action · GitHub](https://github.com/SonarSource/sonarcloud-github-action/blob/master/Dockerfile) refs sonarsource/sonar-scanner-cli:5.0 which just had a new release 5.0.1 which I think introduced this problem

---

<div class="post-metadata">

**Author:** ![Alex\_Lo](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/alex_lo/32/56711_2.png) [@Alex\_Lo](https://community.sonarsource.com/u/Alex_Lo)\
**Post date:** [April 16, 2024, 4:18pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/3 "2024-04-16T16:18:38Z")

</div>

we are using sonarsource/sonarcloud-github-action@master

Issue seems to be [sonarcloud-github-action/Dockerfile at master · SonarSource/sonarcloud-github-action · GitHub](https://github.com/SonarSource/sonarcloud-github-action/blob/master/Dockerfile#L24)

[sonarcloud-github-action/Dockerfile at master · SonarSource/sonarcloud-github-action · GitHub](https://github.com/SonarSource/sonarcloud-github-action/blob/master/Dockerfile) refs sonarsource/sonar-scanner-cli:5.0 which just had a new release 5.0.1 which I think introduced this problem

---

<div class="post-metadata">

**Author:** ![sveinse](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/sveinse/32/56713_2.png) [@sveinse](https://community.sonarsource.com/u/sveinse)\
**Post date:** [April 16, 2024, 4:30pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/5 "2024-04-16T16:30:14Z")

</div>

- GitHub action
- Python
- Project: [GitHub - Laerdal/python-objdictgen at feature-add-sonarcube](https://github.com/Laerdal/python-objdictgen/tree/feature-add-sonarcube)

I’m attempting to make use of SonarCloud in a project and all of the sudden the GitHub action stops working. It fails on `Build SonarSource/sonarcloud-github-action@master`

Any ideas what this can be caused by? It did work and then now fails for some reason. Any proposals what I can do?

```auto
 > [4/6] RUN chmod +x /entrypoint.sh:
  0.471 chmod: /entrypoint.sh: Operation not permitted

```

Failing log report here:

> <https://github.com/Laerdal/python-objdictgen/actions/runs/8708864113/job/23887655799>

Thanks,  
Svein

---

<div class="post-metadata">

**Author:** ![Alex\_Lo](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/alex_lo/32/56711_2.png) [@Alex\_Lo](https://community.sonarsource.com/u/Alex_Lo)\
**Post date:** [April 16, 2024, 4:32pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/6 "2024-04-16T16:32:49Z")

</div>

same issue: [GitHub Actions fail: "chmod: /entrypoint.sh: Operation not permitted"](https://community.sonarsource.com/t/github-actions-fail-chmod-entrypoint-sh-operation-not-permitted/113514)

---

<div class="post-metadata">

**Author:** ![sveinse](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/sveinse/32/56713_2.png) [@sveinse](https://community.sonarsource.com/u/sveinse)\
**Post date:** [April 16, 2024, 4:34pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/7 "2024-04-16T16:34:08Z")

</div>

Same as I see in [Problems running sonarcloud-github-action, fails in docker build](https://community.sonarsource.com/t/problems-running-sonarcloud-github-action-fails-in-docker-build/113518)

---

<div class="post-metadata">

**Author:** ![Alex\_Lo](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/alex_lo/32/56711_2.png) [@Alex\_Lo](https://community.sonarsource.com/u/Alex_Lo)\
**Post date:** [April 16, 2024, 4:36pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/8 "2024-04-16T16:36:14Z")

</div>

some issue in the Dockerfile updates [Comparing 5.0.0.2966...master · SonarSource/sonar-scanner-cli-docker · GitHub](https://github.com/SonarSource/sonar-scanner-cli-docker/compare/5.0.0.2966...master)

---

<div class="post-metadata">

**Author:** ![jrich523](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/jrich523/32/56721_2.png) [@jrich523](https://community.sonarsource.com/u/jrich523)\
**Post date:** [April 16, 2024, 4:40pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/9 "2024-04-16T16:40:27Z")

</div>

We’ve been using the github action for a bit but today its broken, and im not exactly how it broke but the dockerfile fails to build giving this 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
> 
> ```
> 
> * * *
> 
> 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 4.43 seconds before retry.  
> /usr/bin/docker build -t 76388f:2b2dc200edcd4f52bd2ecc41bc8eee3f -f “/home/runner/work/\_actions/sonarsource/sonarcloud-github-action/master/Dockerfile” “/home/runner/work/\_actions/sonarsource/sonarcloud-github-action/master”  
> #0 building with “default” instance using docker driver

It seems like this PR is what broke it

> <https://github.com/SonarSource/sonarcloud-github-action/pull/57/files>

if you try to build it locally it will fail in the same way.

It seems like the `COPY` should include the `--chmod` rather than doing it as a `RUN` which will bypass that problem (or check it in to git as executable)

Either way, i’ve had to remove this from my pipelines for now because of this error

---

<div class="post-metadata">

**Author:** ![sveinse](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/sveinse/32/56713_2.png) [@sveinse](https://community.sonarsource.com/u/sveinse)\
**Post date:** [April 16, 2024, 4:43pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/10 "2024-04-16T16:43:00Z")

</div>

Same as [Problems running sonarcloud-github-action, fails in docker build](https://community.sonarsource.com/t/problems-running-sonarcloud-github-action-fails-in-docker-build/113518)

---

<div class="post-metadata">

**Author:** ![arrmansa](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/arrmansa/32/47123_2.png) [@arrmansa](https://community.sonarsource.com/u/arrmansa)\
**Post date:** [April 16, 2024, 4:51pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/11 "2024-04-16T16:51:45Z")

</div>

I’m having the same issue.

```auto
Step 4/7 : RUN chmod +x /entrypoint.sh
chmod: /entrypoint.sh: Operation not permitted
The command '/bin/sh -c chmod +x /entrypoint.sh' returned a non-zero code: 1

```

The last working digest of sonarsource/sonar-scanner-cli:5.0.1  
was  
Digest: sha256:494ecc3b5b1ee1625bd377b3905c4284e4f0cc155cff397805a244dee1c7d575

The current one with digest

Digest: sha256:c137f8c67272971c001aad747dce830d81d62dce25acd0e4b8ae7290b225657c

is broken and is causing issues with github actions. Maybe something can be changed to roll back to the previous version?

TIA

---

<div class="post-metadata">

**Author:** ![viniciusczar](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/viniciusczar/32/56726_2.png) [@viniciusczar](https://community.sonarsource.com/u/viniciusczar)\
**Post date:** [April 16, 2024, 5:01pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/12 "2024-04-16T17:01:29Z")

</div>

Please, see that:

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

---

<div class="post-metadata">

**Author:** ![rafael-loggi](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/rafael-loggi/32/46469_2.png) [@rafael-loggi](https://community.sonarsource.com/u/rafael-loggi)\
**Post date:** [April 16, 2024, 5:07pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/13 "2024-04-16T17:07:47Z")

</div>

Same here!

---

<div class="post-metadata">

**Author:** ![david-percent](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/david-percent/32/56727_2.png) [@david-percent](https://community.sonarsource.com/u/david-percent)\
**Post date:** [April 16, 2024, 5:09pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/14 "2024-04-16T17:09:03Z")

</div>

Facing the same issue

---

<div class="post-metadata">

**Author:** ![rafael-loggi](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/rafael-loggi/32/46469_2.png) [@rafael-loggi](https://community.sonarsource.com/u/rafael-loggi)\
**Post date:** [April 16, 2024, 5:24pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/15 "2024-04-16T17:24:39Z")

</div>

Same problem here!

---

<div class="post-metadata">

**Author:** ![Tim\_Nordloh](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/tim_nordloh/32/56731_2.png) [@Tim\_Nordloh](https://community.sonarsource.com/u/Tim_Nordloh)\
**Post date:** [April 16, 2024, 5:33pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/16 "2024-04-16T17:33:55Z")

</div>

Same error; started about an hour ago.

---

<div class="post-metadata">

**Author:** ![arrmansa](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/arrmansa/32/47123_2.png) [@arrmansa](https://community.sonarsource.com/u/arrmansa)\
**Post date:** [April 16, 2024, 5:45pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/17 "2024-04-16T17:45:37Z")

</div>

looks like there’s also a github issue for this [https://github.com/SonarSource/sonarqube-scan-action/issues/104](https://github.com/SonarSource/sonarqube-scan-action/issues/104)

---

<div class="post-metadata">

**Author:** ![Alex\_Lo](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/alex_lo/32/56711_2.png) [@Alex\_Lo](https://community.sonarsource.com/u/Alex_Lo)\
**Post date:** [April 16, 2024, 5:56pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/18 "2024-04-16T17:56:13Z")

</div>

> <https://github.com/SonarSource/sonarcloud-github-action/pull/67/files>
>
> Latest release of https://hub.docker.com/r/sonarsource/sonar-scanner-cli breaks …this action as in:
> 
> !\[image\](https://github.com/SonarSource/sonarcloud-github-action/assets/570991/25e1205b-61c9-461f-ba4a-a0b985a496c7)
> 
> Version history of docker image:
> 
> !\[image\](https://github.com/SonarSource/sonarcloud-github-action/assets/570991/0bbb13d4-7870-4365-bc40-57814ef445d5)
> 
> 
> The proposed solution is to keep the GH Action building from the last known good docker image, upgrades to the base docker image should be tested in a branch and then promoted to the main branch (master in this repo)

---

<div class="post-metadata">

**Author:** ![cromerohdz](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/cromerohdz/32/40902_2.png) [@cromerohdz](https://community.sonarsource.com/u/cromerohdz)\
**Post date:** [April 16, 2024, 5:57pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/19 "2024-04-16T17:57:18Z")

</div>

Same here!

---

<div class="post-metadata">

**Author:** ![ianhgraham-rr](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ianhgraham-rr/32/56734_2.png) [@ianhgraham-rr](https://community.sonarsource.com/u/ianhgraham-rr)\
**Post date:** [April 16, 2024, 5:59pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/20 "2024-04-16T17:59:07Z")

</div>

We’re having the same issue.

---

<div class="post-metadata">

**Author:** ![jwhy89](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/jwhy89/32/54377_2.png) [@jwhy89](https://community.sonarsource.com/u/jwhy89)\
**Post date:** [April 16, 2024, 6:10pm UTC](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548/21 "2024-04-16T18:10:48Z")

</div>

Same here.

[Next page](https://community.sonarsource.com/t/outage-sonarscanner-cli-docker-sonarqube-sonarcloud-github-actions/113548.md?page=2)