Skip to content
This repository has been archived by the owner on Apr 28, 2018. It is now read-only.

get-container should take "-name" as a parameter #75

Closed
BenjaminArmstrong opened this issue May 31, 2016 · 4 comments · Fixed by #85
Closed

get-container should take "-name" as a parameter #75

BenjaminArmstrong opened this issue May 31, 2016 · 4 comments · Fixed by #85
Assignees

Comments

@BenjaminArmstrong
Copy link

Pretty hard to get a single container right now

@swernli swernli self-assigned this Jun 1, 2016
@swernli
Copy link
Contributor

swernli commented Jun 1, 2016

This one is a tricky issue... Docker's engine api doesn't give us a graceful way to request one ContainerListResponse object or multiple ContainerResponse objects due to the way their rest endpoints are designed. We'll need to dig further, but it's likely that whatever we do now will be a work-around until the engine api is improved.

@jterry75
Copy link
Contributor

jterry75 commented Jun 1, 2016

I know its 100% less than ideal but we could theoretically just do client side processing for now. IE: get the full list but only write out the one that matches the -Id or -Name requested. We should open a tracking item in Docker to add the /containers/json to support /containers/json?id=<> in the filters list.

@jterry75
Copy link
Contributor

jterry75 commented Jun 1, 2016

Also, I haven't had a chance to try but what if we used since=<id>&limit=1? Is it inclusive?

@swernli
Copy link
Contributor

swernli commented Jun 2, 2016

Oh man... I didn't realize that since and before took ID/name. I thought those were timestamps. I'll give that a try and it could solve our issue (if since/before are inclusive).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants