Tanay and I have been iterating for the last week on why EC2 is failing for us. I manually created an instance identical to the deployed AMI, and explored how things were working:
1) the volume is actually only 15 gigs, NOT 22 gigs. Also, it is mounted to /dev, and not /, which I am wondering whether the docker container will even see this space.
The image below is from inside an EC2 instance, R4.xlarge, on the same AMI deployed by batch:
the volume the docker container is given is NOT on the entire 22 gigs; it is only given 10 gigs
This image below is from inside an EC2 instance, R4.xlarge, inside the docker container:
note that we have a 10 gig partition, not the full 15 gigs that we expected.
ebridge2
commented
7 years ago
Tanay and I have been iterating for the last week on why EC2 is failing for us. I manually created an instance identical to the deployed AMI, and explored how things were working:
1) the volume is actually only 15 gigs, NOT 22 gigs. Also, it is mounted to /dev, and not /, which I am wondering whether the docker container will even see this space.
The image below is from inside an EC2 instance, R4.xlarge, on the same AMI deployed by batch:
the volume the docker container is given is NOT on the entire 22 gigs; it is only given 10 gigs
This image below is from inside an EC2 instance, R4.xlarge, inside the docker container:
note that we have a 10 gig partition, not the full 15 gigs that we expected.