> Large container image failing to start 'first' time Did you see any errors/warnings in agent logs when the container failed to start?
Regards, Qian Zhang On Mon, Aug 19, 2019 at 10:46 PM Marc Roos <[email protected]> wrote: > > I have a container image of around 800MB. I am not sure if that is a > lot. But I have noticed it is probably to big for a default setup to get > it to launch. I think the only reason it launches eventually is because > data is cached and no timeout expires. The container will launch > eventually when you constrain it to a host. > > How can I trace where this timeout occurs? Are there options to specify > timeouts? > > > > > > > >
