Comment 3 for bug 1418803
Revision history for this message
| Ashish Billore (ashish.billore) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
513534c
demo site
(Get the code!)
@LiangChen, regrets for delay on getting back on this.
So, I looked at the possibility of removing the hardcoding and making it configurable, however, my view is this may partially address the problem. Reason being this timeout is related to number of layers in a image being pulled. Even with configurable timeout, this issue will again be seen for images with more layers compared to images with less layers.
I am working on to get the layer or progress of pull and then based on it, wait for it to finish. I am planning to put up a working implemetation by this week and based on how it works for various images (with varying number of layers) will take it forward.
Hope this is fine, thanks.