Comment # 7
on bug 1109
from Nathan Scott
(In reply to comment #6)
> > It's an important usability issue, it absolutely must match Docker
> > behaviour. The whole point of the fuzzy matching is to provide the
> > behaviour that users expect
>
> According to a little experiment here, docker-1.6 (f21) actually behaves
> in the way that I proposed: ambiguous container prefixes are rejected.
OK, sold - we should follow that.
> > (same reason why a docker: prefix on all name was never going to fly).
>
> Then you suffer collisions between docker and non-docker container
> namespaces: something irrelevant to docker end-users but significant
> to a sysadmin with both lxc & docker on the system.
Right, and when we see a real world site like that, then we should start
thinking about this as a non-academic exercise. It's solvable, keeping current
behaviour too - its just the number of people for whom it will ever be an issue
makes it not worth worrying about in the short/medium-term, probably even in
the long term, really.