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.

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

Spike: Use containerd as a runtime for Concourse #3891

Closed
ddadlani opened this issue May 21, 2019 · 4 comments

Comments

@ddadlani
Copy link
Contributor

commented May 21, 2019

No description provided.

@ddadlani ddadlani created this issue from a note in Runtime (Icebox) May 21, 2019

@ddadlani

This comment has been minimized.

Copy link
Contributor Author

commented May 21, 2019

This is technically 2 spikes:

  1. Use containerd (without Garden)
  2. Use docker

@ddadlani ddadlani moved this from Icebox to Backlog in Runtime May 21, 2019

@ddadlani ddadlani changed the title Spike: Use Docker as a runtime for Concourse Spike: Use containerd as a runtime for Concourse Jun 25, 2019

@ddadlani

This comment has been minimized.

Copy link
Contributor Author

commented Jul 8, 2019

Also investigate using an off-the-shelf solution for container networking (e.g. docker/libnetwork) rather than implementing our own

@ddadlani

This comment has been minimized.

Copy link
Contributor Author

commented Jul 8, 2019

Another concern is, how are we going to interface with containerd on the worker?

@vito

This comment has been minimized.

Copy link
Member

commented Sep 4, 2019

Turned this into the containerd workers epic.

@vito vito closed this Sep 4, 2019

Alternate Backends Spike automation moved this from Backlog to Done Sep 4, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
2 participants
You can’t perform that action at this time.