Skip to content

Commit ab62314

Browse files
committed
clean up some anonymization
1 parent 32cbf3f commit ab62314

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

blog/2021/debugging-docker-health-checks.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ Let's assume your container is unhealthy. How can you get more detail than that?
2727
[jq]: https://stedolan.github.io/jq/
2828

2929
```bash
30-
docker inspect --format "{{ "{{json .State.Health }}" }}" iq_platform_jsconfig_mt | jq
30+
docker inspect --format "{{ "{{json .State.Health }}" }}" container_name | jq
3131
```
3232

3333
Just in case you were thinking about not using `jq`, here's the difference in output of the previous command, without and then with jq:
@@ -41,7 +41,7 @@ The only cloud service I have experience with is AWS, so that's the only one I c
4141
Unfortunately AWS doesn't expose the full healthcheck log through their CLI, but you can at least get some sense for it using this command.
4242

4343
```bash
44-
aws ecs describe-tasks --cluster platform-jsconfig-mt --tasks <task-id> | jq '.tasks[0].containers[0]'
44+
aws ecs describe-tasks --cluster <cluster-name> --tasks <task-id> | jq '.tasks[0].containers[0]'
4545
```
4646

4747
Of course this requires you to know the task id (at present, this is a 32 character alphanumeric string), which I imagine you can extract using other aws cli commands if needed -- that's out of scope for this discussion.

0 commit comments

Comments
 (0)