更改源映像时,Docker Web App失去了IP限制! [英] Docker Web App loses IP restriction when I change source image!

查看:75
本文介绍了更改源映像时,Docker Web App失去了IP限制!的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

twitter支持团队建议我在此处发布我的问题.

I was advised by the twitter support team to post my problem here.

我有一个使用我的Azure容器注册表中的映像的Linux Docker Web应用程序.我希望图像不暴露在互联网上,因此我们对将使用此应用程序的服务使用IP限制.假设从ACR拍摄的图像称为: myImage:v1. 当我更改映像时,我用名称将新映像推送到容器注册表中 myImage:v2 .

I have a Linux Docker Web App which uses an image from my Azure Container Registry. I want the Image to NOT be exposed to the internet so we are using IP restriction to the service that will use this app. Let's say the image taken from the ACR is called: myImage:v1. When I do changes to the image I push a new one to the container registry with the name myImage:v2.

Web应用程序现在失去了IP限制,我必须进入门户网站进入IP限制页面,等待几秒钟,然后返回.

The Web App has now LOST the IP restriction, and I have to go into the portal enter the IP restriction page, wait a few secs, and then its back. 

如何防止丢失IP限制?这真的不好.

How can I prevent losing my IP restriction? This is REALLY NOT GOOD.


推荐答案

你好,

您是否已在 Dockerfile 中设置了此限制>? 

Have you setup this restriction in the Dockerfile? 

有一个很好的堆栈溢出 我认为有助于理解如何必须特别拒绝一组IP.

There's a good Stack Overflow post that I think is helpful in understanding how to have to file specifically deny a set of IPs. 


这篇关于更改源映像时,Docker Web App失去了IP限制!的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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