We looked at this a little more and debug output didn't include anything particularly useful; basically, a few layers just hung partially complete forever.
However, when pulling the same image with docker it exhibited the same problem, and it only seemed to impact certain registries (Quay), so I'm suspicious of networking issues or the registry having some problem. Seems like the next possible steps would be going through the fun of ssl mitm + tcpdump, or adding more logging in docker2aci and just downloading with it, or working with Quay's support who might already have better ideas for how to do this sorta thing. Please correct me if I'm getting any details wrong. Best, Euan On Wed, Aug 17, 2016 at 4:59 AM, Jonathan Boulle <[email protected] > wrote: > Never heard of this before - could you please file a bug and include the > output from running the command with `--debug`? Thanks! > > On 16 August 2016 at 19:30, Stefan Vetter <[email protected]> wrote: > >> Hi all, >> >> using rkt v1.12.0 I am experiencing the problem that rkt fetch can >> download all layers, but doesn't do anything afterwards (image is not in >> image list at this state). >> >> Any idea what might be the problem and how this can be fixed? >> >> >> Thanks >> > >
