Broken dependency for docker.io package on Yakkety and Debian

This is only if you have -proposed enabled, right? There is a fix waiting
in the SRU queue for this.

On 4 January 2017 at 21:45, Po-Hsu Lin <email address hidden> wrote:

> Public bug reported:
>
> While trying to install docker.io package, it complains about the
> dependency problem for runc
>
> $ sudo apt-get install docker.io
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
> docker.io : Depends: runc (>= 1.0.0~rc1-0ubuntu2) but
> 1.0.0~rc1-0ubuntu2~16.10.1 is to be installed
> E: Unable to correct problems, you have held broken packages.
>
> ** Affects: docker.io (Ubuntu)
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to
> docker.io in Ubuntu.
> https://bugs.launchpad.net/bugs/1653912
>
> Title:
> Broken dependency for docker.io package on Yakkety
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/
> 1653912/+subscriptions
>

Yep, I encounter this while running the Kernel SRU test.

The two fixes passed SRU, does this still occur with 1.12.6-0ubuntu1~16.10.1?

Hello,

I didn't see this issue during this cycle, please feel free to close this bug.

Thank you!

Marked invalid. Thanks for the update.

Also affects Debian 10, Buster

docker.io : Depends: runc (>= 1.0.0~rc2+git20170201.133.9df8b30~) but 0.1.1+dfsg1-2+b2 is to be installed

Buster versions are not worked out yet, so this bug can be a placeholder for when Buster is released to prod. Encountered this on a testing virtual machine.