Insufficient space in download directory `/var/cache/yum/aarch64/2/amzn2-core`

[0xYao]

• A reproducible test case or series of steps
  • Running cdk deploy devNitroWalletEth for the first time failed at step two of building the Docker image, e.g.

    #5 [2/8] RUN yum install gcc python3 python3-devel net-tools -y
    ...omitted
    #5 0.862 Insufficient space in download directory /var/cache/yum/aarch64/2/amzn2-core
    #5 0.862     * free   0 
    #5 0.862     * needed 100 k
    #5 ERROR: executor failed running [/bin/sh -c yum install gcc python3 python3-devel 
    net-tools -y]: exit code: 1

  • I ran docker image prune -a from this StackOverflow's answer and then I ran cdk deploy devNitroWalletEth again. Now the previous failed step 2 succeeded but it raised the following error

...omitted
#8 [4/8] COPY ./kms/kmstool_enclave_cli ./
#8 sha256:b83fa96953567dac69bd41961d0d0eef8df493c59993f08e559e41033ced844f
#8 ERROR: "/kms/kmstool_enclave_cli" not found: not found

#9 [5/8] COPY ./kms/libnsm.so /usr/lib64/
#9 sha256:48bb7dba25461e915b346522a30982a8b524151b8506fa3edf9656a56dce82dd
#9 ERROR: "/kms/libnsm.so" not found: not found

#5 [2/8] RUN yum install gcc python3 python3-devel net-tools -y
#5 sha256:5285754fb35c10ce153924f74496a0c7e4c5e5f23d6f17967f75a0e112d129a0
#5 CANCELED
------
 > [4/8] COPY ./kms/kmstool_enclave_cli ./:
------
------
 > [5/8] COPY ./kms/libnsm.so /usr/lib64/:
------
failed to compute cache key: "/kms/libnsm.so" not found: not found
...omitted

• So I ran the ./scripts/build_kmstool_enclave_cli.sh command to build the binaries for Nitro Enclaves. Again, it threw the Insufficient space error, e.g.

[builder  7/50] RUN yum install -y gcc-c++:                                                                                                                                                                                                                  
#11 0.433 Loaded plugins: ovl, priorities                                                                                                                                                                                                                       
#11 1.323 213 packages excluded due to repository priority protections                                                                                                                                                                                          
#11 1.636 Resolving Dependencies                                                                                                                                                                                                                                
#11 1.636 --> Running transaction check
#11 1.636 ---> Package gcc-c++.aarch64 0:7.3.1-15.amzn2 will be installed
#11 1.662 --> Finished Dependency Resolution
#11 1.717 
#11 1.717 Dependencies Resolved
#11 1.717 
#11 1.717 ================================================================================
#11 1.717  Package        Arch           Version                  Repository         Size
#11 1.717 ================================================================================
#11 1.717 Installing:
#11 1.717  gcc-c++        aarch64        7.3.1-15.amzn2           amzn2-core         11 M
#11 1.717 
#11 1.717 Transaction Summary
#11 1.717 ================================================================================
#11 1.717 Install  1 Package
#11 1.717 
#11 1.718 Total download size: 11 M
#11 1.718 Installed size: 35 M
#11 1.718 Downloading packages:
#11 1.719 
#11 1.719 
#11 1.719 Error downloading packages:
#11 1.719   gcc-c++-7.3.1-15.amzn2.aarch64: Insufficient space in download directory /var/cache/yum/aarch64/2/amzn2-core/packages
#11 1.719     * free   0 
#11 1.719     * needed 11 M
#11 1.719 
------
executor failed running [/bin/sh -c yum install -y gcc-c++]: exit code: 1

• However, re-executing ./scripts/build_kmstool_enclave_cli.sh one more time worked. The behaviours here are inconsistent and I am not sure why they are happening.

• The version of our code being used

  • Commit 1fa0d541af348f49fc6533e05232ac64b9991f93

• Any modifications you've made relevant to the bug

  • N/A

• Anything unusual about your environment or deployment

  • N/A

[dpdornseifer]

Hi @0xYao, it seems that this error is related to insufficient storage requirements of your docker overlay filesystem. You might want to look into the docker system prune command to free up some space (https://docs.docker.com/engine/reference/commandline/system_prune/).