Hi Bálint,
> I have uploaded docker-runc to unstable (in NEW) for docker.io
> containing previous runc version
Thanks. It has now passed NEW.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Control: block -1 by 877284
Hi,
2017-09-29 11:25 GMT-04:00 Bálint Réczey :
> Hi Chris,
>
> 2017-09-29 10:52 GMT-04:00 Chris Lamb :
>> Hi Bálint,
>>
>>> Which is the first docker.io version that works with runc 1.0.0 rc4? I
>>> would like to add the proper Breaks:.
>>
>> With rc4? None that are in
Hey Bálint,
> How about I upload docker-runc with previous runc version shipping
> docker-runc binary and make docker.io use it by removing this patch hunk?:
(I'm not qualified to comment on the implications of this, alas!)
Best wishes,
--
,''`.
: :' : Chris Lamb
`. `'`
Hi Chris,
2017-09-29 10:52 GMT-04:00 Chris Lamb :
> Hi Bálint,
>
>> Which is the first docker.io version that works with runc 1.0.0 rc4? I
>> would like to add the proper Breaks:.
>
> With rc4? None that are in Debian AFAICT. Perhaps I'm misunderstanding.
Yes, there is none AFAIK.
I see activity
Hi Bálint,
> Which is the first docker.io version that works with runc 1.0.0 rc4? I
> would like to add the proper Breaks:.
With rc4? None that are in Debian AFAICT. Perhaps I'm misunderstanding.
(As in, I was seeing this bug with docker.io 1.13.1~ds1-2, currently in
sid).
Regards,
--
Control: affects -1 docker.io
Hi,
2017-09-29 10:23 GMT-04:00 Chris Lamb :
> Hi,
>
>> update to runc (1.0.0~rc4) breaks docker
>
> I can confirm that downgrading to 1.0.0~rc2+git20170201.133.9df8b30-3
> "fixed" this for me.
Before uploading I asked around on IRC if anyone had problems with
upload
6 matches
Mail list logo
