Control: reassign -1 runc
Since it's trivial to fix in runc, I reassign this to runc now.
It'll be fixed later, which is approved by release team, along with
another improvement in runc.
--
Shengjing Zhu
On 3/6/19 4:55 PM, Dmitry Smirnov wrote:
> This is not such a small and definitely undesirable overhead. Its purpose is
> unclear, it requires manual step and sure enough it will be forgotten.
> Moreover it aims at the problem in another package.
> It is not runc's job to meet Docker
On 3/6/19 10:03 AM, Shengjing Zhu wrote:
> I think the runc should be fixed.
>
> But I don't like the patch you suggested. It's confused to user. If
> you set the git commit to the upstream one, like
> ccb5efd37fb7c86364786e9137e22948751de7ed for 1.0.0-rc6, the user would
> think it's 1.0.0-rc6
On Wednesday, 6 March 2019 12:50:54 PM AEDT Arnaud Rebillout wrote:
> **Solution 1**
> [...]
> One is to patch docker, and fix their code so that it can handle various
> runc version outputs.
I prefer this solution.
> **Solution 2**
>
> The other way is to modify the runc build so that we
Hi Arnaud,
Thanks for the summary.
On Wed, Mar 6, 2019 at 9:51 AM Arnaud Rebillout
wrote:
>
> Dear Go team,
>
> So let met sum up this bug now to avoid you reading the backlog:
>
> In short, docker doesn't recognize the output of `runc --version`, and
> then it misbehaves and flood the log
> On Mar 5, 2019, at 7:50 PM, Arnaud Rebillout
> wrote:
>
> Dear Go team,
>
> So let met sum up this bug now to avoid you reading the backlog:
>
> In short, docker doesn't recognize the output of `runc --version`, and
> then it misbehaves and flood the log forever. To be more accurate,
>
Dear Go team,
So let met sum up this bug now to avoid you reading the backlog:
In short, docker doesn't recognize the output of `runc --version`, and
then it misbehaves and flood the log forever. To be more accurate,
docker is not happy because it wants to know the git commit that was
used to
7 matches
Mail list logo
