Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DockerClient.list should be able to figure out which Docker image and ports are associated with each container #207

Closed
wallrj opened this issue Jul 7, 2014 · 5 comments · Fixed by #878
Closed

DockerClient.list should be able to figure out which Docker image and ports are associated with each container #207

wallrj opened this issue Jul 7, 2014 · 5 comments · Fixed by #878
Assignees
@dwgebler
Labels
component: orchestration
Milestone
Release 0.3

Comments

@wallrj
Copy link
Contributor

wallrj commented Jul 7, 2014

We're not populating this information yet. Originally we were using geard so this was an issue, but with Docker directly it's easy.
@wallrj wallrj mentioned this issue Jul 7, 2014
Closed
@wallrj
Copy link
Contributor Author

wallrj commented Jul 7, 2014

See openshift/geard#229

@itamarst
Copy link
Contributor

itamarst commented Jul 7, 2014

This is not necessary for 0.1 since we're not going to be addressing changes to the application config.

@itamarst itamarst mentioned this issue Jul 11, 2014
Closed
2 tasks
@itamarst itamarst mentioned this issue Jul 22, 2014
Merged
@itamarst itamarst mentioned this issue Aug 15, 2014
Closed
1 task
@wallrj wallrj mentioned this issue Aug 15, 2014
Closed
@exarkun exarkun mentioned this issue Aug 21, 2014
Closed
9 tasks
@itamarst itamarst added this to the Release 0.3 milestone Sep 17, 2014
@itamarst itamarst changed the title GearClient.list should be able to figure out which Docker image is associated with each Gear unit DockerClient.list should be able to figure out which Docker image is associated with each container Sep 17, 2014
@itamarst itamarst changed the title DockerClient.list should be able to figure out which Docker image is associated with each container DockerClient.list should be able to figure out which Docker image and ports are associated with each container Sep 17, 2014
@itamarst itamarst added ready and removed ready labels Sep 24, 2014
@itamarst itamarst mentioned this issue Sep 30, 2014
Merged
@dwgebler dwgebler self-assigned this Oct 1, 2014
@dwgebler
Copy link
Contributor

dwgebler commented Oct 1, 2014

@robhaswell @exarkun @itamarst
Can this be labelled ready? I can't see any obvious reason for this issue to be blocked now.

@itamarst
Copy link
Contributor

itamarst commented Oct 1, 2014

One thing this branch should include is expanding the IDockerClient tests to cover adding ports and images.

@exarkun exarkun mentioned this issue Oct 3, 2014
Merged
@dwgebler
Copy link
Contributor

dwgebler commented Oct 6, 2014

I'll estimate this at 1.5 days and see what happens....

dwgebler added a commit that referenced this issue Oct 6, 2014
@dwgebler
design for #207
b27a72f
@dwgebler dwgebler mentioned this issue Oct 6, 2014
Closed
@exarkun exarkun removed the design label Oct 6, 2014
dwgebler added a commit that referenced this issue Oct 7, 2014
@dwgebler
patch code referencing #207 to make use of image from DockerClient.li…
c3161c0 
…st()
@dwgebler dwgebler mentioned this issue Oct 7, 2014
Merged
@dwgebler dwgebler removed the review label Oct 7, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dwgebler dwgebler

Labels
component: orchestration
Projects
None yet
Milestone
Release 0.3
Development

Successfully merging a pull request may close this issue.

Dockerclient list images ports 207 ClusterHQ/flocker
5 participants
@exarkun @robhaswell @dwgebler @wallrj @itamarst