2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Hello,
In order to fix this issue, you need to update the dm.base value in the docker configuration. Please refer this article to achieve the same.
https://aws.amazon.com/premiumsupport/knowledge-center/batch-job-failure-disk-space/
répondu il y a 4 ans
0
Thanks Anish, that helped. For anyone also having trouble with this, you need to
- increase the size of the disk available to docker (/dev/xvdcz) in the launch template
- increase the disk quota available to each container in the launch template, I used:
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="==BOUNDARY=="
--==BOUNDARY==
Content-Type: text/cloud-boothook; charset="us-ascii"
#cloud-boothook
#!/bin/bash
cloud-init-per once docker_options echo 'OPTIONS="${OPTIONS} --storage-opt dm.basesize=30G"' >> /etc/sysconfig/docker
--==BOUNDARY==
Content-Type: text/x-shellscript; charset="us-ascii"
#!/bin/bash
# more aggressive settings for cleaning up old tasks
echo ECS_ENGINE_TASK_CLEANUP_WAIT_DURATION=1m >> /etc/ecs/ecs.config
echo ECS_IMAGE_CLEANUP_INTERVAL=1m >> /etc/ecs/ecs.config
echo ECS_IMAGE_MINIMUM_CLEANUP_AGE=1m >> /etc/ecs/ecs.config
--==BOUNDARY==--
répondu il y a 4 ans
Contenus pertinents
- demandé il y a 10 mois
- demandé il y a 9 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans