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.
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
containerd executor should be smarter about containerd events subscription #2219
Comments
Thanks! I'll leave this here at least until #2275 is merged I think. |
Correct containerd link: containerd/containerd#1066 |
ijc
added a commit
to ijc/swarmkit
that referenced
this issue
Mar 23, 2018
It targets an old pre v1.0 alpha version of containerd and is not currently maintained. closes moby#2219, closes moby#2258, closes moby#2259 and closes moby#2299. The vendoring of libtrust did not become obsolete here but vndr noted that it was unused so I dropped it while I was there. Signed-off-by: Ian Campbell <ijc@docker.com>
ijc
added a commit
to ijc/swarmkit
that referenced
this issue
Mar 23, 2018
It targets an old pre v1.0 alpha version of containerd and is not currently maintained. closes moby#2219, closes moby#2258, closes moby#2259 and closes moby#2299. The vendoring of libtrust did not become obsolete here but vndr noted that it was unused so I dropped it while I was there. Signed-off-by: Ian Campbell <ijc@docker.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The containerd executor added in #1965 currently starts a containerd event stream for every task. These event streams contain events for all containers which containerd is managing. We should either:
My preference is to do the former.
The text was updated successfully, but these errors were encountered: