./containerlaunch.sh: line 6: update-ca-certificates: command not found

Rodrigo 20

I'm using App Service to launch a docker container. It was working perfectly fine!

Then, a day ago, the app stops to work, and in the logs, I see this (below)

I don't own containerlaunch.sh file, it should be from Azure.

What I'm doing wrong?

2023-05-17T11:33:13.888836835Z ./containerlaunch.sh: line 6: update-ca-certificates: command not found
2023-05-17T11:33:13.898826553Z Updated CA certificates
2023-05-17T11:50:14.463204566Z ./containerlaunch.sh: line 6: update-ca-certificates: command not found
2023-05-17T11:50:14.486848458Z Updated CA certificates
2023-05-17T11:50:54.115862067Z ./containerlaunch.sh: line 6: update-ca-certificates: command not found
2023-05-17T11:50:54.119680808Z Updated CA certificates

brtrach-MSFT 15,256 Reputation points Microsoft Employee

2023-05-18T22:42:14.02+00:00
The error message indicates that the update-ca-certificates command is not found. This command is used to update the certificate authority (CA) certificates on the system.

It is possible that the update-ca-certificates command is not installed on the container image you are using. You can try installing it by adding the following command to your Dockerfile:

RUN apt-get update && apt-get install -y ca-certificates

This will install the ca-certificates package, which includes the update-ca-certificates command.

If you are using a different package manager, you can use the appropriate command to install the ca-certificates package.

Once you have added this command to your Dockerfile, rebuild your container image and redeploy it to Azure App Service.

Let us know if you run into any issues with the above approach by replying to this message. We would be happy to assist you further.
Rodrigo 20 Reputation points

2023-05-19T11:42:39.7533333+00:00

The base image has already ca-certificates installed. The problem is on App Service; I don't know what it is trying to do.
Vladimir Pavlenko 5 Reputation points

2023-05-19T13:53:01.75+00:00

Hello, I am facing the same issue starting today!

The issue appears only when I define an Authentication Provider (Microsoft Azure AD Auth flow)
Rahul Saraf 5 Reputation points

2023-05-19T20:53:06.7733333+00:00

I am also suddenly getting this error
Rahul Saraf 5 Reputation points

2023-05-19T21:04:05.5366667+00:00

I have added the command:

RUN apt-get update && apt-get install -y ca-certificates

to dockerfile but it still same issue. What kind of issue is this. MS needs to resolve this ASAP.
brtrach-MSFT 15,256 Reputation points Microsoft Employee

2023-05-20T00:23:08.57+00:00

We have created a ticket with the product group since this seems to be a platform issue. We are waiting on their response but hope to have more to share early next week.
brtrach-MSFT 15,256 Reputation points Microsoft Employee

2023-05-23T02:33:07.0033333+00:00

@Rodrigo @Rahul Saraf @Vladimir Pavlenko We have received feedback from other customers that this issue appears to be resolved. Can you please check your containers to see if you also are now resolved? Thank you
Vladimir Pavlenko 5 Reputation points

2023-05-23T07:42:39.9833333+00:00

Hello @brtrach-MSFT ! Thank you for your update. I'm still facing the same issue :(
Rahul Saraf 5 Reputation points

2023-05-23T09:01:18.98+00:00

Hello @brtrach-MSFT Our problem is still not resolved.
brtrach-MSFT 15,256 Reputation points Microsoft Employee

2023-05-23T16:02:30.64+00:00

Okay, yes, the resolution only seemed to work briefly. We will continue to push for updates from the product group.
Arturo 10 Reputation points

2023-05-23T19:26:41.6333333+00:00

You realize by not fixing this and it has already been 5 days, it is breaking people's ability to deploy fixes to any type of environment when this does not work. Furthermore, when we deploy to an environment we are actually breaking the app service, thank god we read this post before deploying any fixes to Production. I hope the Product team understands the urgency in fixing this.
Arturo 10 Reputation points

2023-05-24T18:59:32.4+00:00

Any updates on this issue? @brtrach-MSFT
Vladimir Pavlenko 5 Reputation points

2023-05-25T07:08:35.5333333+00:00

Any updates on this one?

The issue is blocking our team from delivering a new product!!!!
brtrach-MSFT 15,256 Reputation points Microsoft Employee

2023-05-25T18:22:39.8266667+00:00

@Rodrigo @Rahul Saraf @Vladimir Pavlenko @Arturo

This issue has been escalated within the product group and is receiving the necessary attention.

One item that is confusing us is that we do not see any failed starts of the containers in our logs. Are you using Azure Gov? If not, can you please explain the behavior that is impacting your apps? Since the container is starting, it's not clear what is breaking due to the cert issue.

These details will help us further build the fix. Thank you for your help and continued patience on this matter.
Vladimir Pavlenko 5 Reputation points

2023-05-26T09:54:46.6366667+00:00

@brtrach-MSFT

The behaviour is clearly shown in the screenshot that I have sent before.

The middleware container cannot find ./containerlaunch.sh command which is causing it to fail (I suppose, as I don't see any failure logs, I still receive HTTP code 500 when calling the web app).

2 answers

brtrach-MSFT 15,256 Reputation points Microsoft Employee

2023-05-26T20:24:08.9833333+00:00

The latest update is that the product group is going to roll out a fix for the CA cert error and we do not expect this to cause any issues for customers.

Without more concrete evidence, it appears that customers had change their configuration settings, which likely broke the deployment of the app. The ca-cert error was more of a coincidence rather than the cause of the containers not working.

If someone else can provide further context as to why or how the ca-cert broke their site, please reply to this message.
Please sign in to rate this answer.
brtrach-MSFT 15,256 Reputation points Microsoft Employee

2023-05-26T23:18:43.2+00:00

To add further context, this is the current belief because the cert that is providing the error is not used by Azure commercial customers. This cert that is providing errors is only used by a very limited number of Azure customers.

That is what leads us to believe this is related to misconfiguration on the apps end. For apps that we reviewed internally, each app had its configurations settings changed before the issues were reported.

For now, we suggest reverting the configuration settings. If assistance is needed in troubleshooting the configuration settings, please reach out to your support engineer. If you do not have a support ticket, please reply to this message.

Vladimir Pavlenko 5 Reputation points

2023-05-29T09:16:45.5666667+00:00

Hello @brtrach-MSFT . Was the fix for the CA cert error rolled out?
Sign in to comment
brtrach-MSFT 15,256 Reputation points Microsoft Employee

2023-06-03T01:01:29.86+00:00

@Vladimir Pavlenko The final update regarding this is there will be a hotfix rolling out here in the next couple of days. This hotfix should reach customers sometime next week.

Thank you for your patience on this matter.
Please sign in to rate this answer.
Vladimir Pavlenko 5 Reputation points

2023-06-05T11:29:52.6033333+00:00

@brtrach-MSFT , Thank you for the update.
Sign in to comment