Scott Dodson
Scott Dodson
> @deads2k @sdodson Has this come up before? Poking around to see what I can find. This seems to have happened upstream via kubeadm(https://github.com/kubernetes/kubeadm/issues/2200) but we won't pick those changes...
I think given we're only warning people against using loopback rather than disabling it all together that docker should still start if d-s-s fails. We provide plenty of ongoing feedback...
Sorry, I see from the #60 that we're looking at making loopback opt-in. If that's the case then fine with making d-s-s mandatory
would you expect this to also address adding version specific flags automatically? For instance docker-1.9.1 added `dm.use_deferred_deletion=true` and it'd be nice to get that during upgrades by merging machine generated...
So this issue can be closed then, right? Probably a different issue, but If I upgrade from docker-1.8.2 to docker-1.9.1, assuming d-s-s runs when docker starts, will I get the...
Accepting this test threshold change directly into 4.9 as these tests have been reimplemented in later releases.
/override ci/prow/e2e-gcp-builds
This test does not seem likely to be affected by this change, we will investigate to make sure that there's a bug filed to track looking into it.