How many containers are you all running?
-
There is a post about getting overwhelmed by 15 containers and people not wanting to turn the post into a container measuring contest.
But now I am curious, what are your counts?
I would guess those of you running k*s would win out by pod scalingdocker ps | wc -l
For those wanting a quick count.
-
There is a post about getting overwhelmed by 15 containers and people not wanting to turn the post into a container measuring contest.
But now I am curious, what are your counts?
I would guess those of you running k*s would win out by pod scalingdocker ps | wc -l
For those wanting a quick count.
$ docker ps | wc -l 14Just running 13 myself.
-
There is a post about getting overwhelmed by 15 containers and people not wanting to turn the post into a container measuring contest.
But now I am curious, what are your counts?
I would guess those of you running k*s would win out by pod scalingdocker ps | wc -l
For those wanting a quick count.
Server 1: 5 containers
Server 2: 4 containers
Server 3: 4 containers
Server 4: 61 containersBasically if a container is a resource hog, it gets moved somewhere with more resources or specialized hardware.
-
Server 1: 5 containers
Server 2: 4 containers
Server 3: 4 containers
Server 4: 61 containersBasically if a container is a resource hog, it gets moved somewhere with more resources or specialized hardware.
That's a wee bit imbalanced. Is server 4 your big boi?
-
There is a post about getting overwhelmed by 15 containers and people not wanting to turn the post into a container measuring contest.
But now I am curious, what are your counts?
I would guess those of you running k*s would win out by pod scalingdocker ps | wc -l
For those wanting a quick count.
0, it's all organised nicely with nixos
-
0, it's all organised nicely with nixos
Boooo, you need some chaos in your life. :D
-
There is a post about getting overwhelmed by 15 containers and people not wanting to turn the post into a container measuring contest.
But now I am curious, what are your counts?
I would guess those of you running k*s would win out by pod scalingdocker ps | wc -l
For those wanting a quick count.
- Because I'm old, crusty, and prefer software deployments in a similar manner.
-
- Because I'm old, crusty, and prefer software deployments in a similar manner.
I salute you and wish you the best in never having a dependency conflict.
-
There is a post about getting overwhelmed by 15 containers and people not wanting to turn the post into a container measuring contest.
But now I am curious, what are your counts?
I would guess those of you running k*s would win out by pod scalingdocker ps | wc -l
For those wanting a quick count.

64 containers in total, 60 running - the remaining 4 are Watchtowers that I run manually whenever I feel like it (and have time to fix things if something should break).
-

64 containers in total, 60 running - the remaining 4 are Watchtowers that I run manually whenever I feel like it (and have time to fix things if something should break).
What tool is that screenshot from?
-
There is a post about getting overwhelmed by 15 containers and people not wanting to turn the post into a container measuring contest.
But now I am curious, what are your counts?
I would guess those of you running k*s would win out by pod scalingdocker ps | wc -l
For those wanting a quick count.
59 according to
docker info. -
59 according to
docker info.Hot damn. That is a far better way then counting the lines from docker ps
-
There is a post about getting overwhelmed by 15 containers and people not wanting to turn the post into a container measuring contest.
But now I am curious, what are your counts?
I would guess those of you running k*s would win out by pod scalingdocker ps | wc -l
For those wanting a quick count.
I know using work as an example is cheating, but around 1400-1500 to 5000-6000 depending on load throughout the day.
At home it's 12.
-
I know using work as an example is cheating, but around 1400-1500 to 5000-6000 depending on load throughout the day.
At home it's 12.
I was watching a video yesterday where an org was churning 30K containers a day because they didn't profile their application correctly and scaled their containers based on a misunderstanding how Linux deals with CPU scheduling.