Hi @demobox 

These are just things I discovered while writing an integration with 
github.com/zettio/weave which auto-creates containers that have no SSH daemon, 
hence no inbound port 22, and jclouds still wants to enumerate them.

The image ID issue happens because jclouds is cacheing image data, and when you 
are committing changes in stages to a container a new image with a new ID is 
created, which cannot then be found. The original image ID you started from is 
still there, but intermediate ones are not. Maybe this should have been solved 
by changing the cache parameters for images in the Docker provider?

I will add some updated tests before this is merged...

I believe @andreaturli is working on updates to handle the new 1.14 API in the 
next release of Docker.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/89#issuecomment-58725712

Reply via email to