Re:Docker in Production: A History of Failure
by strange_quark on Friday November 04, 2016 @11:49AM
(#12873504)
You have to use devicemapper in direct-lvm mode in order to get free space back. I agree it's not the best out-of-box experience, but so far we haven't had any problems running ECS on CentOS instances since switching to direct-lvm.
Re:Docker in Production: A History of Failure
by coleca on Friday November 04, 2016 @12:45PM
(#12873931)
Yes, although loopback mode for devicemapper is the out of the box configuration for Docker even though Docker themselves doesn't recommend it for production. I had tons of issues w/devicemapper on CentOS 7 (kernel panics causing AWS to mark the host as unhealthy and kill it off) that I was finally only able to resolve by switching to AUFS under Ubuntu 16.04, which has worked pretty well for me. Knock on wood, AUFS has been pretty solid so far.
Re:Docker in Production: A History of Failure
by bergwolf on Friday November 04, 2016 @01:14PM
(#12874181)
except when it comes to a many-level-image, AUFS performance degrades dramatically
Re:Docker in Production: A History of Failure
by patmcguire on Friday November 04, 2016 @11:33AM
(#12873363)
Yup, this is how I wound up with a 45 GB image on my development machine after futzing around with Docker for two hours. Does the same with OS X.
You know that trick the post mentions about how you have to keep removing images to stop your machines running out of disk space? Yeah, removing images doesn't actually reclaim disk space on devicemapper (!!):
https://github.com/docker/docker/issues/3182
Oh, and devicemapper is the only natively supported storage backend on the AWS official AMI.