基于microsoft / windowsservercore的大容器映像无法在容器的Web应用程序中启动 [英] Large container image based on microsoft/windowsservercore failed to start in web app for container

查看:63
本文介绍了基于microsoft / windowsservercore的大容器映像无法在容器的Web应用程序中启动的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们部署了一个基于微软/ windowsservercore的大型16GByte自定义容器映像。成功拉出容器后,在Web应用程序内启动失败并显示以下日志文​​件


Docker客户端错误。无法启动容器。容器:feb7f2151c702735775c0ebec2c9407bbd4510236f82619eb4de07f1eb30e3a6。 StatusCode:InternalServerError。消息:Docker API响应状态代码= InternalServerError,response = {" message":" container
feb7f2151c702735775c0ebec2c9407bbd4510236f82619eb4de07f1eb30e3a6在CreateContainer期间遇到错误:Windows系统调用失败:无法与虚拟机建立连接托管容器。 (0xc0370108) 


这里有什么问题?

解决方案

< blockquote>

您究竟要尝试部署什么?只是为了隔离,它在当地工作正常吗?您能否确认,哪个父图像是您利用' microsoft / iis:windowsservercore- ltsc2016,
最新'或'microsoft / aspnet:4.7.2-windowsservercore-ltsc2016,4.7.2,最新'?请参阅

使用不同的父图像


默认情况下,Azure App Service中部署的所有Windows容器都限制为2GB RAM。您可以通过提供以下设置来更改此值:
作为应用程序设置 - CONTAINER_MEMORY:以MB为单位定义,并且必须< =到主机的总物理内存,然后检查是否有帮助。


容器的Web App当前允许您只向外界公开一个端口。这意味着您的容器只能
在单个端口上侦听HTTP请求。 
请参阅
document
,了解有关此主题的更多详细信息。


要以JSON格式获取有关当前Docker日志的更多详细信息,您可以导航到此位置:
https:// [sitename] .scm.azurewebsites.net / api / logs / docker


We deployed a large 16GByte custom container image based on microsoft/windowsservercore. After successfully pulling the container start failed inside the web app with following logfile entry

Docker client error. Failed to start container. Container: feb7f2151c702735775c0ebec2c9407bbd4510236f82619eb4de07f1eb30e3a6. StatusCode: InternalServerError. Message: Docker API responded with status code=InternalServerError, response={"message":"container feb7f2151c702735775c0ebec2c9407bbd4510236f82619eb4de07f1eb30e3a6 encountered an error during CreateContainer: failure in a Windows system call: A connection could not be established with the Virtual Machine hosting the Container. (0xc0370108) 

What could be our problem here?

解决方案

How exactly are you attempting to deploy? Just to isolate, does it work locally fine? Could you confirm, which parent image are you leveraging ‘microsoft/iis:windowsservercore-ltsc2016, latest’ or ‘microsoft/aspnet:4.7.2-windowsservercore-ltsc2016, 4.7.2, latest’? See, Use a different parent image.

By default, all Windows Containers deployed in Azure App Service are limited to 2GB RAM. You can change this value by providing the following setting as an app setting - CONTAINER_MEMORY: defined in MB and must be <= to the total physical memory of the host, and then check to see if that helps.

Web App for Containers currently allows you to expose only one port to the outside world. That means that your container can only listen for HTTP requests on a single port. See this document for more details on this topic.

To fetch more details on the current Docker logs in JSON format, you can navigate to this location: https://[sitename].scm.azurewebsites.net/api/logs/docker


这篇关于基于microsoft / windowsservercore的大容器映像无法在容器的Web应用程序中启动的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆