Skip to content
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.

Evaluate how we configure docker (and nodes in general) for Kubernetes #236

Closed
colemickens opened this issue Feb 2, 2017 · 4 comments
Closed

Comments

@colemickens
Copy link
Contributor

This is regarding the scramble we had two weeks ago for the docker upgrade breaking clusters.

See the upstream issue: kubernetes/kubernetes#40182 which features suggestions beyond pinning to 1.12.x. Additionally, it's suggested that we simply tell docker to not configure iptables at all.

This partially serves as a reminder to see if sig-node has a list of published guidelines. If not, pinging thockin after he's back from vacation to see if he's aware of a list.

Also, as a reminder to watch upstream to see how they handle it (a patch in Kube, a recommendation to change docker's config json, etc).

@colemickens
Copy link
Contributor Author

We should look at the doc that @brendandburns sent around from Deis when we do this.

@colemickens
Copy link
Contributor Author

Also, we need to keep this under consideration for 1.6 and newer addon manager, etc:

@colemickens
Copy link
Contributor Author

Also:
kubelet.go:1145] Image garbage collection failed: unable to find data for container /.

@anhowe
Copy link
Contributor

anhowe commented May 1, 2017

closing as not specific enough.

@anhowe anhowe closed this as completed May 1, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants