2 ms·
The major problem with very large containers is that it can cause failed jobs in container schedulers due to the holdoff timer expiring before the container is
by ty_a 9y ago
The major problem with very large containers is that it can cause failed jobs in container schedulers due to the holdoff timer expiring before the container is even downloaded. I've only seen this with Marathon so far but I've not yet tried to launch a 2GB container in k8s.
- alberteinstein 9y agoThis doesn't happen on Kubernetes. The Pod stays in ContainerCreating state unless the entire image is pulled. We are running some Java containers which are >2GB and apart from the time it takes to start-up on a fresh node, everything is fine.