On Mon, Jan 23, 2012 at 4:05 PM, Serge Hallyn
<serge.hallyn@xxxxxxxxxxxxx> wrote:
>
> I've been playing for the last week with ways to fix this, and in the
> end I can see two ways.
How about a third way:
- make "newinstance" mandatory (and "-o newinstance" is a no-op) and
forget about the whole issue.
- if you really want to remount the old global one, you have to use a
bind mount of that original mount instead.
There may be some subtle reason why the above is totally broken and
just fundamnetally wouldn't work, and breaks all existing setups, but
maybe it's worth at least discussing as an option?
Or did I entirely misunderstand the problem?
Linus
_______________________________________________
Containers mailing list
Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/containers
