Azure DevOps:docker-compose over SSH普通消息解释为错误 [英] Azure DevOps: docker-compose over SSH normal messages interpreted as error

问题描述

docker-compose，普通消息被解释为Azure DevOps中的错误

我在Azure DevOps中具有发布管道，在该管道中，我通过 SSH 连接到服务器，并与其他命令一起运行 docker-compose up 命令.

问题是正常消息会被解释为错误，因此即使一切成功，释放也会失败.

此版本发布后，一切都已启动并运行.

有人知道为什么这些消息被解释为错误吗?

我发现docker将这些消息写到 stderr 而不是 stdout .在SSH任务的Azure DevOps管道中，有 STDERR失败选项，默认情况下会选中该选项.当我取消选中此选项时，即使消息被标记为错误，发行版也不会再失败.

真正令我困扰的是，即使出现一些实际错误，也将被忽略.我真的不知道他们为什么设计这样，但这是另一个话题.

链接: https://github.com/docker/compose/issues/5296

docker-compose, normal messages interpreted as errors in Azure DevOps

I have Release pipeline in Azure DevOps where I'm connecting to to server trough SSH and running docker-compose up command along with others.

Problem is that normal messages are interpreted as errors so release fails even when everything was successful.

After this release everything is up and running.

Does anyone know why these messages were interpreted as errors?

解决方案

I found out that docker writes those messages to stderr instead of stdout. In Azure DevOps pipeline in SSH task there is option Fail on STDERR which is checked by default. When I uncheck this option release no longer fails on this step even messages are marked as error.

What really bothers me is that now even when some real error occurs, it will be ignored. I really don't know why they designed is like this, but that's for another topic.

Links: https://github.com/docker/compose/issues/5296

这篇关于Azure DevOps:docker-compose over SSH普通消息解释为错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！