Azure app service pulling image failure error

Question

Azure app service pulling image failure error

Sankar Gopalakrishnan 50

Hi,

I have an azure app service(Linux based) with publishing model as ‘Container’.

I am using private Artifactory to pull docker images from as container registry. I am able to pull sample .Net 6.0 web api from the registry and successfully run.

For some reason, I cant pull one of our application .net 6.0 web apis. I verified that docker files are same for both apis.

The error I am receiving is strange. It says “Unsupported image manifest. The manifest with version ‘application/vnd.docker.distribution.manifest.v1+json’ has not been supported yet.

I also verified that the manifest has ‘application/vnd.oci.image.config.v1+json’.

Can someone please help.

Grmacjon-MSFT 19,511 Reputation points Moderator

2024-05-31T18:05:50.68+00:00

Hi @Sankar Gopalakrishnan thanks for bringing this to our attention.

Can you review the Docker image manifest file (usually located at <image_name>@<tag>/manifest.json) to make sure it only contains the application/vnd.oci.image.config.v1+json media type? Since the error message mentions the unsupported application/vnd.docker.distribution.manifest.v1+json format it's possible that both formats might be present in the manifest which is why you're getting this error
Sankar Gopalakrishnan 50 Reputation points

2024-05-31T18:09:26.8166667+00:00

Thanks for the response @Grmacjon-MSFT Yes. I verified the manifest.json file and it contains only application/vnd.oci.image.config.v1+json
Sankar Gopalakrishnan 50 Reputation points

2024-05-31T18:12:02.99+00:00

Hi. Thank you for your response @Grmacjon-MSFT Yes. I verified that my manifest.json file contains only application/vnd.oci.image.config.v1+json
Grmacjon-MSFT 19,511 Reputation points Moderator

2024-05-31T19:45:03.6533333+00:00

@Sankar Gopalakrishnan thanks for the update. I will check internally with the engineering team to see if this a potential bug and get back to you. Is this the first time you encounter this issue or has this happened before?
Sankar Gopalakrishnan 50 Reputation points

2024-05-31T19:52:01.4833333+00:00

I am facing this issue for the padt few weeks. Actually, we just started with containers and Azure app service. @Grmacjon-MSFT
Grmacjon-MSFT 19,511 Reputation points Moderator

2024-05-31T19:58:48.4733333+00:00

Okay, got it. Lastly can you please share the Azure doc you're following so we can repro this from our end?
Sankar Gopalakrishnan 50 Reputation points

2024-05-31T20:07:49.2466667+00:00

@Grmacjon-MSFT there is no one specific doc. I referred to few docs actually. Like I said I am using private artifactory as container registry. There is no issue with running .net 6.0 sample web api. I created a .net 6 web api project in visual studio, I pushed the image to my artifactory, pulled from azure app service and am able to run it. There no issues with connections or anything as far as I know. The issue is with another api project where I use same base image(aspnet:6.0), same docker file and same manifest version
Grmacjon-MSFT 19,511 Reputation points Moderator

2024-05-31T21:12:46.79+00:00

okay, thanks for the information. I will share this with the engineering team and get back to you
Anonymous

2024-06-11T07:24:36.4+00:00

I am facing the exact same issue, but with a python docker container on Azure Function App hosted on an ASEv3. Our entire infra deployment is done with Bicep and both the bicep files and dockerfile have not changed since the last successful deployment.

I'm very much looking forward to hearing what the issue could be. EDIT: For us it turned out that there was a typo in the container repo/image name in ACR. This meant that the function/web app was looking for an inexistent image name, and failed with this misleading error message.
Vivencio P. Malinao Jr 0 Reputation points

2024-06-27T18:00:42.7033333+00:00

Hi,

Is this already resolved? If yes, what was the root cause and how was it fixed? We are also facing this error when the function app is trying to pull the image from a private repository.

Looking forward to hear some answers :)
Sankar Gopalakrishnan 50 Reputation points

2024-06-27T19:16:58.7666667+00:00

@Vivencio P. Malinao Jr No solutions yet. This issue still persists
Grmacjon-MSFT 19,511 Reputation points Moderator

2024-07-20T00:20:24.1866667+00:00

@Sankar Gopalakrishnan Vivencio P. Malinao Jr Tobias Kleine we are sorry to hear you're still facing this problem. The engineering team is working to resolve this issue. Please us your

App name via email to AzCommunity[at]Microsoft[dot]com with the email subject: <Attn - Grace> so we can assist you with this issue offline.

Thanks,

Grace
Wojciech Jakubowski 46 Reputation points

2024-07-24T15:57:32.9733333+00:00

Please check if your image name is correct. In my case that was the problem. I had exactly the same error message and the root cause was a typo in the image name.
Sarva Bhowma Jarubula 0 Reputation points

2025-01-13T10:36:47.88+00:00

Hello,

I was wondering if there has been any progress on the issue we've been facing when deploying the image from the private registry to the webapp. We are encountering the same problem, and my findings are as follows: We are building an open container image that generates the specific media type, 'application/vnd.oci.image.index.v1+json'. However, the webapp is unable to recognize that this is an OCI image and is instead trying to consider it as a 'application/vnd.docker.distribution.manifest.v1+json' Docker distributed image.

I believe that if there were an option to identify whether this is an OCI or Docker image, the webapp could be adjusted accordingly. Please let me know if there are any updates on this issue. Thank you for your help.

Anonymous

Hey @Grmacjon-MSFT I have the same issue with my image built by podman.
here is the azure build pipeline I'm using

- script: 'sudo podman build --no-cache --format docker -f ./ci-cd/keycloak.Dockerfile -t dpdhl.css-qhcr-pi.azure.deutschepost.de/gedas/iam:${{ parameters.version }} . '
            displayName: Build IAM image version ${{ parameters.version }}
          
- script: |
              sudo podman trust key load ~/.docker/trust/private/71782ddf4966e5d23b8f153bc33893e0d40101c7be71cc68e0cd52518a0466e8.key
              sudo podman image sign --sign-by $(css-imagesign-root-passphrase) dpdhl.css-qhcr-pi.azure.deutschepost.de/gedas/iam:${{ parameters.version }}
              sudo podman push --format v2s2 dpdhl.css-qhcr-pi.azure.deutschepost.de/gedas/iam:${{ parameters.version }}
            displayName: Sign and push Image

Anonymous

Hey @Grmacjon-MSFT I am facing same issue with image built by podman (unfortunately, we can't use docker directly)
build pipeline is

- script: 'sudo podman build --no-cache --format docker -f ./ci-cd/keycloak.Dockerfile -t dpdhl.css-qhcr-pi.azure.deutschepost.de/gedas/iam:${{ parameters.version }} . '
            displayName: Build IAM image version ${{ parameters.version }}
          
- script: |
              sudo podman trust key load ~/.docker/trust/private/71782ddf4966e5d23b8f153bc33893e0d40101c7be71cc68e0cd52518a0466e8.key
              sudo podman image sign --sign-by $(css-imagesign-root-passphrase) dpdhl.css-qhcr-pi.azure.deutschepost.de/gedas/iam:${{ parameters.version }}
              sudo podman push --format v2s2 dpdhl.css-qhcr-pi.azure.deutschepost.de/gedas/iam:${{ parameters.version }}
            displayName: Sign and push Image
            env:

1 answer

Your answer

Grmacjon-MSFT 19,511 Reputation points Moderator

2024-05-31T18:05:50.68+00:00

Hi @Sankar Gopalakrishnan thanks for bringing this to our attention.

Can you review the Docker image manifest file (usually located at <image_name>@<tag>/manifest.json) to make sure it only contains the application/vnd.oci.image.config.v1+json media type? Since the error message mentions the unsupported application/vnd.docker.distribution.manifest.v1+json format it's possible that both formats might be present in the manifest which is why you're getting this error
Sankar Gopalakrishnan 50 Reputation points

2024-05-31T18:09:26.8166667+00:00

Thanks for the response @Grmacjon-MSFT Yes. I verified the manifest.json file and it contains only application/vnd.oci.image.config.v1+json
Sankar Gopalakrishnan 50 Reputation points

2024-05-31T18:12:02.99+00:00

Hi. Thank you for your response @Grmacjon-MSFT Yes. I verified that my manifest.json file contains only application/vnd.oci.image.config.v1+json
Grmacjon-MSFT 19,511 Reputation points Moderator

2024-05-31T19:45:03.6533333+00:00

@Sankar Gopalakrishnan thanks for the update. I will check internally with the engineering team to see if this a potential bug and get back to you. Is this the first time you encounter this issue or has this happened before?
Sankar Gopalakrishnan 50 Reputation points

2024-05-31T19:52:01.4833333+00:00

I am facing this issue for the padt few weeks. Actually, we just started with containers and Azure app service. @Grmacjon-MSFT
Grmacjon-MSFT 19,511 Reputation points Moderator

2024-05-31T19:58:48.4733333+00:00

Okay, got it. Lastly can you please share the Azure doc you're following so we can repro this from our end?
Sankar Gopalakrishnan 50 Reputation points

2024-05-31T20:07:49.2466667+00:00

@Grmacjon-MSFT there is no one specific doc. I referred to few docs actually. Like I said I am using private artifactory as container registry. There is no issue with running .net 6.0 sample web api. I created a .net 6 web api project in visual studio, I pushed the image to my artifactory, pulled from azure app service and am able to run it. There no issues with connections or anything as far as I know. The issue is with another api project where I use same base image(aspnet:6.0), same docker file and same manifest version
Grmacjon-MSFT 19,511 Reputation points Moderator

2024-05-31T21:12:46.79+00:00

okay, thanks for the information. I will share this with the engineering team and get back to you
Anonymous

2024-06-11T07:24:36.4+00:00

I am facing the exact same issue, but with a python docker container on Azure Function App hosted on an ASEv3. Our entire infra deployment is done with Bicep and both the bicep files and dockerfile have not changed since the last successful deployment.

I'm very much looking forward to hearing what the issue could be. EDIT: For us it turned out that there was a typo in the container repo/image name in ACR. This meant that the function/web app was looking for an inexistent image name, and failed with this misleading error message.
Vivencio P. Malinao Jr 0 Reputation points

2024-06-27T18:00:42.7033333+00:00

Hi,

Is this already resolved? If yes, what was the root cause and how was it fixed? We are also facing this error when the function app is trying to pull the image from a private repository.

Looking forward to hear some answers :)
Sankar Gopalakrishnan 50 Reputation points

2024-06-27T19:16:58.7666667+00:00

@Vivencio P. Malinao Jr No solutions yet. This issue still persists
Grmacjon-MSFT 19,511 Reputation points Moderator

2024-07-20T00:20:24.1866667+00:00

@Sankar Gopalakrishnan Vivencio P. Malinao Jr Tobias Kleine we are sorry to hear you're still facing this problem. The engineering team is working to resolve this issue. Please us your

App name via email to AzCommunity[at]Microsoft[dot]com with the email subject: <Attn - Grace> so we can assist you with this issue offline.

Thanks,

Grace
Wojciech Jakubowski 46 Reputation points

2024-07-24T15:57:32.9733333+00:00

Please check if your image name is correct. In my case that was the problem. I had exactly the same error message and the root cause was a typo in the image name.
Sarva Bhowma Jarubula 0 Reputation points

2025-01-13T10:36:47.88+00:00

Hello,

I was wondering if there has been any progress on the issue we've been facing when deploying the image from the private registry to the webapp. We are encountering the same problem, and my findings are as follows: We are building an open container image that generates the specific media type, 'application/vnd.oci.image.index.v1+json'. However, the webapp is unable to recognize that this is an OCI image and is instead trying to consider it as a 'application/vnd.docker.distribution.manifest.v1+json' Docker distributed image.

I believe that if there were an option to identify whether this is an OCI or Docker image, the webapp could be adjusted accordingly. Please let me know if there are any updates on this issue. Thank you for your help.
Anonymous

2025-02-07T04:19:43.9233333+00:00

Hey @Grmacjon-MSFT I have the same issue with my image built by podman.
here is the azure build pipeline I'm using

- script: 'sudo podman build --no-cache --format docker -f ./ci-cd/keycloak.Dockerfile -t dpdhl.css-qhcr-pi.azure.deutschepost.de/gedas/iam:${{ parameters.version }} . ' displayName: Build IAM image version ${{ parameters.version }} - script: | sudo podman trust key load ~/.docker/trust/private/71782ddf4966e5d23b8f153bc33893e0d40101c7be71cc68e0cd52518a0466e8.key sudo podman image sign --sign-by $(css-imagesign-root-passphrase) dpdhl.css-qhcr-pi.azure.deutschepost.de/gedas/iam:${{ parameters.version }} sudo podman push --format v2s2 dpdhl.css-qhcr-pi.azure.deutschepost.de/gedas/iam:${{ parameters.version }} displayName: Sign and push Image
Anonymous

2025-02-07T04:25:56.29+00:00

Hey @Grmacjon-MSFT I am facing same issue with image built by podman (unfortunately, we can't use docker directly)
build pipeline is

- script: 'sudo podman build --no-cache --format docker -f ./ci-cd/keycloak.Dockerfile -t dpdhl.css-qhcr-pi.azure.deutschepost.de/gedas/iam:${{ parameters.version }} . ' displayName: Build IAM image version ${{ parameters.version }} - script: | sudo podman trust key load ~/.docker/trust/private/71782ddf4966e5d23b8f153bc33893e0d40101c7be71cc68e0cd52518a0466e8.key sudo podman image sign --sign-by $(css-imagesign-root-passphrase) dpdhl.css-qhcr-pi.azure.deutschepost.de/gedas/iam:${{ parameters.version }} sudo podman push --format v2s2 dpdhl.css-qhcr-pi.azure.deutschepost.de/gedas/iam:${{ parameters.version }} displayName: Sign and push Image env:

Answer 1

Robbie Hanson 0

I got this error repeatedly when my image didn't exist. I had a typo in the folder name.

0 comments

Share via

Azure app service pulling image failure error

1 answer

Your answer