Alex Soto

Sure, no worries :)

I have run the built twice but it is failing in all cases.

Things to do: - [ ] Implement the `newApp` method. - [ ] Update docs - [ ] Write an ftest

Well the error message comes from Docker Host, I will suggest to see why docker sending this message.

We will take a look when we have time, but the errors comes from Docker host for sure, maybe because something wrong in Arquillian Cube (although we have a lot...

@dipak-pawar when you have 5 minutes can you take a look at this? @RajAsapu can you manually delete any network created previously and try it again?

Now it works all the time? What I suspect is that network was started manually before or jvm crashed during tests and network was there El 11 jul. 2017 8:24...

It does not seem a problem with cube since the exception occurs when arquillian is validating deployment file. Have you tried the same example but wihtout using Cube? Which App...

Then try outside cube, just for example embedded wildfly using chameleon https://github.com/arquillian/arquillian-container-chameleon or scaffolding with Forge to check where is exactly the problem.

So this is a f8 kubernetes client issue that should be controlled there? Maybe we could open an issue there so they are aware.