Ya! thanks for following up @daniel-thewatkins , I was just about to message you as I found you helped to resolve another previous docker image related bug 1645463 with @tianon.
> we should find a less invasive fix.
What would you have in mind. Is there another way we could resolve this upstream, or should we turn to the user to make a patch to the source.list before use, e.g. modifying the downstream debootstrap additionally for docker to make the fix per trusty? https://github.com/moby/moby/blob/9a9fc01af8fb5d98b8eec0740716226fadb3735c/contrib/mkimage/debootstrap#L67
Ya! thanks for following up @daniel-thewatkins , I was just about to message you as I found you helped to resolve another previous docker image related bug 1645463 with @tianon.
> we should find a less invasive fix.
What would you have in mind. Is there another way we could resolve this upstream, or should we turn to the user to make a patch to the source.list before use, e.g. modifying the downstream debootstrap additionally for docker to make the fix per trusty? /github. com/moby/ moby/blob/ 9a9fc01af8fb5d9 8b8eec074071622 6fadb3735c/ contrib/ mkimage/ debootstrap# L67
https:/