unionfs

multiple volumes to single target directory?

可紊 提交于 2019-12-07 02:39:52
问题 Is there a way to mount multiple volumes from a host to form a single target mount point? A bit like this: docker run --name ubuntu_bash \ --rm --interactive --tty \ --volume=/media/Large/videos:/videos \ --volume=/media/Small/videos:/videos \ ubuntu find /videos I'm guessing the answer is no but with "overlay" having so many meanings in the context of Docker it's a bit difficult to search for this on the web. If not, is there a Docker Store image that might help? Unfortunately a lot of

multiple volumes to single target directory?

时光怂恿深爱的人放手 提交于 2019-12-05 07:03:51
Is there a way to mount multiple volumes from a host to form a single target mount point? A bit like this: docker run --name ubuntu_bash \ --rm --interactive --tty \ --volume=/media/Large/videos:/videos \ --volume=/media/Small/videos:/videos \ ubuntu find /videos I'm guessing the answer is no but with "overlay" having so many meanings in the context of Docker it's a bit difficult to search for this on the web. If not, is there a Docker Store image that might help? Unfortunately a lot of Docker images don't give sufficient instructions on how to use them. There's no built in docker method to do

docker commit running container

ぃ、小莉子 提交于 2019-11-30 06:50:09
When committing a running container with docker commit , is this creating a consistent snapshot of the filesystem? I'm considering this approach for backing up containers. You would just have to docker commit <container> <container>:<date> and push it to a local registry. The backup would be incremental, as the commit would just create a new layer. Also would the big amount of layers hurt io performance of the container drastically? Is there a way to remove intermediate layers at a later point in time? Edit By consistent I mean that every application that is designed to survive a power-loss

docker commit running container

余生颓废 提交于 2019-11-29 07:16:46
问题 When committing a running container with docker commit , is this creating a consistent snapshot of the filesystem? I'm considering this approach for backing up containers. You would just have to docker commit <container> <container>:<date> and push it to a local registry. The backup would be incremental, as the commit would just create a new layer. Also would the big amount of layers hurt io performance of the container drastically? Is there a way to remove intermediate layers at a later