I agree that the -- logic is a terrible hack. To solve it for real, though, I was thinking we should just make unique names and keep track of what names we've used, rather than parsing the names for our pattern. I'm OK with this patch in the interim, though.

Yeah.
Does docker allow us to attach arbitrary data to a container's info? Or maybe go with nested containers? Although, that'd probably mean that any managed containers would die if the kubelet died, I'm not sure how I feel about that...

Yeah, the kubelet would have to store the mapping persistently, or possibly apiserver can pre-generate globally unique ids for this purpose (a la #199). It's a requirement that containers keep running even if kubelet restarts, so any subcontainer design would have to take that into account.

Cool. #199 looks like the ticket.

On Sat, Jun 21, 2014 at 2:05 PM, Daniel Smith notifications@github.com
wrote:

Yeah, the kubelet would have to store the mapping persistently, or
possibly apiserver can pre-generate globally unique ids for this purpose (a
la #199 #199).
It's a requirement that containers keep running even if kubelet restarts,
so any subcontainer design would have to take that into account.

—
Reply to this email directly or view it on GitHub
#200 (comment)
.