-
Notifications
You must be signed in to change notification settings - Fork 783
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rainbond应用模版导出的镜像名称和tag都否与构建时候选择的镜像名称和tag保持一致 #1554
Comments
Title: Whether the image name and tag exported by the rainbond application template are consistent with the image name and tag selected during construction |
能否具体说下你的使用场景呢?为什么会单独load这个镜像到新的服务器上? 如果你是想在新服务器上重新部署该业务,使用应用模版的导出功能,再导入即可啊,不会涉及到你自己处理这个镜像的过程。 |
Can you describe your use case in detail? Why is this image loaded separately to the new server? If you want to redeploy the business on the new server, you can use the export function of the application template and then import it, which will not involve the process of processing the image yourself. |
开发环境如果使用rainbond,客户现场环境不允许部署rainbond的情况下,只能导出docker-compose格式的文件和镜像使用。
另外测试通过jenkins 调用rainbond的 Webhook 进行组件镜像更新的时候,我jenkins打包的镜像与rainbond上触发组件更新的新命名的镜像不一致,
虽然调用Webhook 返回200 成功,但是看起来不直观。
在 2023-02-21 09:38:34,"yangkaa" ***@***.***> 写道:
能否具体说下你的使用场景呢?为什么会单独load这个镜像到新的服务器上?
如果你是想在新服务器上重新部署该业务,使用应用模版的导出功能,再导入即可啊,不会涉及到你自己处理这个镜像的过程。
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
导出的镜像能与构建的时候选择的镜像名称和tag 可以保持一致吗,不然我镜像load到一台新服务器上镜像根本区分不开。
The text was updated successfully, but these errors were encountered: