* Adding a mount after container is running?
@ 2010-11-03 9:52 Michael Tokarev
0 siblings, 0 replies; only message in thread
From: Michael Tokarev @ 2010-11-03 9:52 UTC (permalink / raw)
To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA
Hello.
What is the way to add a new filesystem mount to
an already running container? I want to "propagate"
a newly created filesystem, or another part of host
filesystem, to a container without restarting it.
I can imagine a way to "propagate" a new filesystem -
by (maybe temporarily) granting access for the
block device in question to the container and
doing a real mount from there. I'm not sure if
it's equivalent to a bind-mount in terms of
resulting behavour (I sent this question to
lkml a few mins ago), but at least this is
easily doable.
But if I want to add a part of existing filesystem
tree to my container, things becomes somewhat less
clean. Still doable in a similar way - by mounting
it in container in a temp place, bind-mounting a
needed part to the right place, and umounting the
temp one. But it's not clean ;)
Is there a better way?
Thanks!
/mjt
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2010-11-03 9:52 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-11-03 9:52 Adding a mount after container is running? Michael Tokarev
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox