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

[bugzilla-daemon@xxxxxxxxxxx]

Comment # 2 on bug 1109 from Frank Ch. Eigler

> Hmm.  By design, what is supposed to be happening is the "fully qualified"
> name (once looked up via the docker fuzzy matching, just like the docker
> client tools do) is returned to the requesting PMDA, which can then use it
> as a unique identifier going forward in subsequent requests - rendering this
> a non-issue.

Even if this were done, it still makes the mapping non-deterministic,
because more than one container can match that substring; a client has
no way of knowing whether its choice was unique.  Emulating the docker
client's apparent non-determinism is not obviously necessary.

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

---

      You are receiving this mail because:

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