情绪 docker 容器无法到达计费端点
我正在尝试使用官方 Docker 映像从 Azure 认知服务运行情绪分析。 Azure 语言认知服务资源已在 Azure 中启动并运行，但容器无法到达计费终结点。
容器按照文档中的描述启动（使用正确的计费和密钥）：
docker run --rm -it -p 5010:5000 --name sentiment_cmd mcr.microsoft.com/azure-cognitive-services/textanalytics/sentiment Eula=accept Billing=https://RESOURCENAME.cognitiveservices.azure.com/ ApiKey=KEY
但结果我总是
Failed to reach billing endpoint: 'Resource temporarily unavailable'. Trying 9 more times.
fail: Microsoft.CloudAI.Containers.Http.CloudClient[0]
Failed to reach billing endpoint: 'Resource temporarily unavailable'. Trying 9 more times.
尝试更改 docker 引擎选择的默认 IP 子网，但它没有解决问题。有什么想法吗？
I am trying to run Sentiment analysis from Azure Cognitive Services using an official docker image. Azure Cognitive Service for Language resource is up and running in Azure, but the container can't reach the Billing endpoint.
The container is started as described in the documentation (with the correct billing and key):
docker run --rm -it -p 5010:5000 --name sentiment_cmd mcr.microsoft.com/azure-cognitive-services/textanalytics/sentiment Eula=accept Billing=https://RESOURCENAME.cognitiveservices.azure.com/ ApiKey=KEY
but in result I always get
Failed to reach billing endpoint: 'Resource temporarily unavailable'. Trying 9 more times.
fail: Microsoft.CloudAI.Containers.Http.CloudClient[0]
Failed to reach billing endpoint: 'Resource temporarily unavailable'. Trying 9 more times.
I tried changing the default IP subnet choosen by docker engine, but it didn't fix the issue. Any ideas?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
正如您所说，Azure 语言认知服务服务已启动并正在运行。问题出在子网上。需要检查计费端点是否与应用程序的子网一起运行。检查计费是在私有子网还是公共子网以及应用程序中。即使服务正在运行，但它仍然没有响应。检查网络连接。检查网络流量是否存在同样的问题。连接前重置或重新检查密钥。
As you are telling the Azure Cognitive Services for Language service is up and running. The problem is with the subnet. Need to check with whether billing endpoint is running with the subnet of the applications is running. Check whether the billing is in private or public subnet and also application is. Even though the service is running and if still it is not responding. Check with the network connections. Check with the network traffic also for the same issue. Reset or recheck the key before connecting.