nturaga / bioconductoroncontainers

Workshop for Bioc2019 for using Bioconductor on containers

Hi there 👋

bioconductoroncontainers's Issues

Docker image and container storage space

BioconductorOnContainers/vignettes/Bioconductor_Containers_Workshop.Rmd

Lines 61 to 66 in d432a5a

	It is important to note, every time you start a container from an image
	it will take up the same amount of space as the image before you build
	on it. So, if you start a docker image of 1GB, the container takes up
	1GB. The space being used on your machine is now 2GB. If you start 5
	containers, they take up 1GB each for a container, so you are
	consuming 5GB space.

My understanding is this is not the case. Docker makes use of copy-on-write technology wherever possible, so that files from the image are not duplicated when you start a container. In fact, you can use docker system df -v to see the actual space usage for individual containers, which is usually quite low.

https://medium.com/@nagarwal/docker-containers-filesystem-demystified-b6ed8112a04a
https://docs.docker.com/v17.09/engine/userguide/storagedriver/imagesandcontainers/
https://docs.docker.com/engine/reference/commandline/system_df/

Do you need docker running on the AMI?

Hi, @nturaga.

I have been using Docker for putting together the workshop materials for everyone (as opposed to an AMI). Do you have a need to actually run docker commands on the AMI, or are you planning on walking through this with folks on their own machines or on GCP? I am asking because docker-in-docker is tricky, so I would probably want to avoid it.

Thanks,
Sean