Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

Proxy restart shouldn't kill containers #1551

Merged
merged 2 commits into from
Oct 19, 2015

Conversation

paulbellamy
Copy link
Contributor

Fixes #1547.

First commit stops it killing containers when restarting the proxy.

Second adds a first pass at an attachment retry mechanism. Thoughts on that? I need to have a think about how to test it.

@rade
Copy link
Member

rade commented Oct 16, 2015

Please split part 2 into a separate issue and PR - I doubt that is going to make it into 1.2.0, whereas part 1 should.

@paulbellamy paulbellamy force-pushed the 1547-proxy-restart-no-kill-containers branch from 89ed4c2 to a0f0367 Compare October 19, 2015 10:22
@paulbellamy paulbellamy changed the title [WIP] proxy restart no kill containers Proxy restart shouldn't kill containers Oct 19, 2015
@paulbellamy paulbellamy assigned rade and unassigned paulbellamy Oct 19, 2015
for _, apiContainer := range containers {
container, err := proxy.client.InspectContainer(apiContainer.ID)
if err != nil {
Log.Warningf("unable to attach existing container %s since inspecting it failed: %v", apiContainer.ID, err)

This comment was marked as abuse.

@rade rade assigned paulbellamy and unassigned rade Oct 19, 2015
@paulbellamy paulbellamy force-pushed the 1547-proxy-restart-no-kill-containers branch from 07ae38a to ace6c01 Compare October 19, 2015 12:53
@paulbellamy paulbellamy assigned rade and unassigned paulbellamy Oct 19, 2015
@rade rade added this to the 1.2.0 milestone Oct 19, 2015
rade added a commit that referenced this pull request Oct 19, 2015
…ontainers

Proxy restart shouldn't kill containers

Fixes #1547.
@rade rade merged commit db9229f into master Oct 19, 2015
@rade rade deleted the 1547-proxy-restart-no-kill-containers branch October 19, 2015 12:55
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 this pull request may close these issues.

2 participants