System.AggregateException, (Docker API responded with status code=BadRequest, response={"message":"network

[skryshtafovych]

BUG REPORT

After Pushing Images to Azure container registry and pulling latest docker-compose code down into Azure CLI i get Below error when the container set starts up with commands.

az webapp config container set --resource-group "" --name "" --multicontainer-config-type compose --multicontainer-config-file docker-compose.yml

ERROR - Container start failed for dockercomposeappletgi_influxdb_0 with System.AggregateException, One or more errors occurred. (Docker API responded with status code=BadRequest, response={"message":"network dockercomposeappletgi_multi_nw__0 is ambiguous (29 matches found on name)"}
) (Docker API responded with status code=BadRequest, response={"message":"network dockercomposeappletgi_multi_nw__0 is ambiguous (29 matches found on name)"}
)
InnerException: Docker.DotNet.DockerApiException, Docker API responded with status code=BadRequest, response={"message":"network dockercomposeappletgi_multi_nw__0 is ambiguous (29 matches found on name)"}

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Using Docker-Compose Inside Azure App Service v3

What happened:
When deploying with azure CLI i get above error. This worked Previously no workflow change.

What you expected to happen:
The container set to be deployed

[skryshtafovych]

According to Microsoft:

This is a known issue and Product Group is currently investigating.
As a workaround please try the following which has worked for other customers:
In container settings, select single container, select any image from the registry and click save.
Once the Save is success, select Docker Compose on the same page and click Save again.
Wait for some time to check if the issue is resolved by browsing the site.

Step Below is What Fixed it For My Config

If the above steps do not resolve the issue, please perform a scale up/down operation from the portal:
Scale up the App service plan to S1n or p1V2, click Apply and once scaleup is done, check if the site is up.
Once site is up, you can scale back down to original tier.

[bigal91]

i can confirm this issue. Habing the same in our Azure WebApp Service in a Docker-Compose environment.

Its been more than a week. Is there any updates on this? If the Product Group is investigating since that time (for an already known bug) I'd assume there might be some sort of progress?

[andywhardy]

Has there been any progress on this issue? We are also hitting it.

The workarounds mentioned only work for a short period of time.

[Ravenzmynd]

Ran into this issue today and the above didn't work. The issue was on an App Service slot. We corrected by deleting the app service slot and recreating. App Service is back to normal now

[Rakatashii]

Continuing to see this whenever the property WEBSITES_ENABLE_APP_SERVICE_STORAGE is set to true. Has any progress been made?

[apchirinoc]

I have this issue too. Have there been any progress?

[vparmeland]

Hello,

Same issue

[manisripathi]

Hello,

Having the similar issue in Linux Web App for Container Azure App Service. Ran into this issue and the app is not responding anymore. Kudu was not responding and the resource was disconnected from log analytics.

I ended up creating another instance and it helped to bring the app live again. Is there any resolution to this issue or any workaround would be helpful.

2022-04-15T18:55:53.061Z ERROR - Container start failed for app-xxx.xxxxx with System.AggregateException, One or more errors occurred. (Docker API responded with status code=InternalServerError, response={"message":"mkdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/xxxx: no space left on device: unknown"}) (Docker API responded with status code=InternalServerError, response={"message":"mkdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/xxxx: no space left on device: unknown"})InnerException: Docker.DotNet.DockerApiException, Docker API responded with status code=InternalServerError, response={"message":"mkdir /var/lib/containerd/io.containerd.runtime.v1.linux/moby/xxxx: no space left on device: unknown"}