{"push_id":904843015,"size":1,"distinct_size":1,"ref":"refs/heads/cr-boucher","head":"2586cd79a67d838f21cdb05b1ac6c80561ef8174","before":"fa45ca03dce36b18cbf838f16d3fa9c5c2d724ca","commits":[{"sha":"2586cd79a67d838f21cdb05b1ac6c80561ef8174","author":{"email":"4b05cea9641ab3f4544bc7c6e600aab00faa2e7f@google.com","name":"Saied Kazemi"},"message":"Don't give up on ENOTEMPTY error when removing containers\n\nWhen checkpointing and restoring the same container multiple times,\ndocker rm -f <CID> can fail with an error indicating that its root\nfilesystem could not be removed because it's not empty.  Turns out that\nfor some unknown reason, hostconfig.json is still in the directory.\nThis patch calls os.RemoveAll() a maximum of 10 times if it fails.\n\nThe issue may be related to the observation that hostconfig.json\nis created several times when a container is started or restored.\nEach time the new hostconfig.json overwrites the previous one, so at the\nend there's only one hostconfig.json but it was created multiple times!\n\nSigned-off-by: Saied Kazemi <saied@google.com>","distinct":true,"url":"https://api.github.com/repos/SaiedKazemi/docker/commits/2586cd79a67d838f21cdb05b1ac6c80561ef8174"}]}