From the course: Docker on AWS

Discover container state

From the course: Docker on AWS

Start my 1-month free trial

Discover container state

“

- [Instructor] So, in our clusters we often have a number of tasks running, and in our simple example we just have a single service with a couple of tasks, but if we look at the fargate service, you can see we actually have desired five and running five, but if you recall in our previous examples, we were really trying to get to just a single container, or maybe a double container sort of an environment. So, why do we have five running? Let's go have a look and see what the environment looks like right now, and maybe we can figure out what's going on with those tasks and underlying containers. If we look, we can see even just at this current state, we have a number of version seven, in my case it's probably version two, or maybe version three in your case, of the hostname-fargate task definition running. One of them is in provisioning state, which means that one of them must have died and was then started over again. If we refresh this, I think we'll see a different set. Provisioning and running so clearly there's something wrong, but the key is that we can learn what's going on with the state of our resources just by looking at the task definitions. We can also look at the task itself so we can sort of drill down a little bit into the task, and we can get the state of this particular instance. In this case, it's currently in running state. My expectation is that eventually this task will also be stopped for some reason, and we'll look at some of the ways that that might happen, or at least some of the ways to further figure out what might be causing this because it gets to a running state, and the basics of that state are pretty obvious. It's running so it should be fine. So, why is it being stopped?

Contents