4 ms·
Sounds a lot like the host OS is generic instead of container-focused, which could be part of the problem. What was the cause/solution? Images too big?
by sierra1011 2y ago
Sounds a lot like the host OS is generic instead of container-focused, which could be part of the problem.
What was the cause/solution? Images too big?
- FooBarWidget 2y agoActually, no, the host OS was Amazon BottleRocket, a specifically container-focused OS. The cause was indeed images being too big. Images — not only the raw images, but also their extracted contents on the filesystem — count towards ephemeral storage too. In their case they can't even control the size of the images because those are supplied by a vendor. The solution was to increase the node's disk space.
- sierra1011 2y agoInteresting, I use Bottlerocket on my work clusters too. I think we had issues like this using some ridiculous data tool images that take up gigabytes, so we just upped the EBS size. Easily done.