[Bug 1109] fuzzy container hex-id naming leads to nondeterminism

[bugzilla-daemon@xxxxxxxxxxx]

Comment # 3 on bug 1109 from Nathan Scott

(In reply to comment #2)
> a client has
> no way of knowing whether its choice was unique.

A user can choose to use unique names at any time, this fuzzy matching is only
there to give users the behaviour they know and expect based on using the
Docker tools.

> We could instead say that the name matching is done exactly once (at
> connection time), and fails if ambiguous.

No, definitely not - that's not sensible behaviour from the users point of
view.
People expect to be able to specify containers just like they would with Docker
- we have already seen this from several people using this already (without it,
would have seen several bug reports & confusion).

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 (same reason why a docker: prefix on all names was never going to fly).

---

      You are receiving this mail because:

• You are on the CC list for the bug.
• You are the assignee for the bug.