AWS AmazonECS documentation change
Summary
Removed the word 'above' from troubleshooting instructions for disk space issues
Security assessment
Change improves clarity but doesn't alter security guidance about log management or container storage. No evidence of addressing vulnerabilities or security features.
Diff
diff --git a/AmazonECS/latest/developerguide/task_cannot_pull_image.md b/AmazonECS/latest/developerguide/task_cannot_pull_image.md index 1db56ee42..400fbc8ad 100644 --- a//AmazonECS/latest/developerguide/task_cannot_pull_image.md +++ b//AmazonECS/latest/developerguide/task_cannot_pull_image.md @@ -142 +142 @@ Example output: -In some cases, the root volume might be filled out by a running container. If the container is using the default `json-file` log driver without a `max-size` limit, it may be that the log file is responsible for most of that space used. You can use the `docker ps` command to verify which container is using the space by mapping the directory name from the output above to the container ID. For example: +In some cases, the root volume might be filled out by a running container. If the container is using the default `json-file` log driver without a `max-size` limit, it may be that the log file is responsible for most of that space used. You can use the `docker ps` command to verify which container is using the space by mapping the directory name from the output to the container ID. For example: