So what's the next step here? is there a change you would like me to make
to the docker packaging or are you going to fix this on your end?
On 30 September 2017 at 09:01, Tim Van Steenburgh <email address hidden>
wrote:
> We did some testing of docker 1.13.1 with CDK this week and it doesn't
> work out-of-the-box, at least not with Flannel on AWS (and Flannel is
> our default overlay at the moment). TL;DR is there's a new default
> iptables rule that breaks us. We can probably work around this in the
> charms, but for now we should keep 1.13.1 in xenial-proposed.
>
> ** Tags removed: verification-needed-xenial
> ** Tags added: verification-failed-xenial
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1712954
>
> Title:
> upgrade to 1.13
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/
> 1712954/+subscriptions
>
So what's the next step here? is there a change you would like me to make
to the docker packaging or are you going to fix this on your end?
On 30 September 2017 at 09:01, Tim Van Steenburgh <email address hidden>
wrote:
> We did some testing of docker 1.13.1 with CDK this week and it doesn't needed- xenial failed- xenial /bugs.launchpad .net/bugs/ 1712954 /bugs.launchpad .net/ubuntu/ +source/ docker. io/+bug/ +subscriptions
> work out-of-the-box, at least not with Flannel on AWS (and Flannel is
> our default overlay at the moment). TL;DR is there's a new default
> iptables rule that breaks us. We can probably work around this in the
> charms, but for now we should keep 1.13.1 in xenial-proposed.
>
> ** Tags removed: verification-
> ** Tags added: verification-
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> upgrade to 1.13
>
> To manage notifications about this bug go to:
> https:/
> 1712954/
>