App Service重启后，如何防止生产插槽上的最新Docker映像更新? [英] How to prevent an update of latest Docker image on production slot after an App Service reboot ?

问题描述

您好，问题在于App Service上的两个插槽用于容器.我解释了这种情况:

Hello, the problem is with the swap between 2 slots on App Service for container. I explain the scenario:

1)我部署了"api:latest"登台插槽上的Docker映像

1) I deploy my "api:latest" Docker image on staging slot

2)我在暂存槽和生产槽之间进行了交换(因此我的"api:latest" Docker映像现在在生产槽中，而先前版本的"api:latest"在暂存槽上)

2) I apply a swap between staging and production slots (so my "api:latest" Docker image is now on production slot and the previous version of "api:latest" is on staging slot)

3)现在，我构建了新版本的"api:latest" Docker映像，该映像已部署在暂存插槽中

3) Now, I build a new version of my "api:latest" Docker image, which is deployed on staging slot

4)问题是:如果重新启动了我的应用服务(自动或手动)，我还将获得最新版本的"api:latest". * production *插槽上的Docker映像.我的问题是:如何保留"api:latest"的先前版本? 生产插槽上的Docker映像?或者，还有另一种方法可以正确管理部署在多个插槽上的Docker映像吗?

4) And the problem is: if my App Service is restarted (automatically or manually), I get also the latest version of my "api:latest" Docker image on *production* slot. My question is: how can I keep the previous version of my "api:latest" Docker image on production slot? Or, is there another method to correctly manage Docker images deploy on multiple slots?

感谢您的帮助，

Micaël

推荐答案

如果您要为docker映像配置粘到插槽(不交换)"这样的设置，到目前为止，这是不可能的.你可以投票 这里.您在这些论坛中分享的所有反馈将由负责构建Azure的Microsoft工程团队监视和审查.

If you want to configure setting like "stick to a slot (not swapped)" for docker image, as of now it is not possible. You may up-vote here. All of the feedback you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Azure.

这篇关于App Service重启后，如何防止生产插槽上的最新Docker映像更新?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！