AMO 🐶⛺🌳

_From @Overdrivr on August 9, 2017 4:25_ I wasn't sure how to debug this further, so no updates so far. I wasn't seeing anything in my object storage logs.

_From @galbacarys on August 18, 2017 16:45_ Having watched this carefully (I know, great way to debug things) I noticed something interesting-It looks like some of the minio requests are...

_From @dumyan on August 18, 2017 21:59_ Hey, guys, you can try with a newer minio image - just edit the minio deployment. Rereading this made me vaguely remember that...

_From @battlemidget on August 19, 2017 20:16_ @dumyan What new minio image are you referring to?

_From @dumyan on August 20, 2017 12:10_ @battlemidget the OP is using minio as a storage backend for the registry. The default image for `deis-minio` is pretty outdated (or at...

_From @battlemidget on August 20, 2017 20:21_ @dumyan thanks im hitting this same issue, ill give that a try

_From @battlemidget on August 21, 2017 17:27_ @dumyan Ok, so not exactly the same issue as this one it seems. I am using off cluster storage (s3) and our distribution...

_From @bacongobbler on August 21, 2017 18:52_ @battlemidget you may want to read our latest blog post. https://deis.com/blog/2017/deis-workflow-final-release/

_From @battlemidget on August 21, 2017 18:58_ @bacongobbler well that is disappointing :(

_From @timfpark on April 5, 2017 15:41_ Deleting the router pod manually with kubectl seems to resolve this.