{"action":"opened","issue":{"url":"https://api.github.com/repos/docker/containerd/issues/584","repository_url":"https://api.github.com/repos/docker/containerd","labels_url":"https://api.github.com/repos/docker/containerd/issues/584/labels{/name}","comments_url":"https://api.github.com/repos/docker/containerd/issues/584/comments","events_url":"https://api.github.com/repos/docker/containerd/issues/584/events","html_url":"https://github.com/docker/containerd/issues/584","id":210869740,"number":584,"title":"Default runtime and highe level orchestration support","user":{"login":"mcastelino","id":7387737,"avatar_url":"https://avatars1.githubusercontent.com/u/7387737?v=3","gravatar_id":"","url":"https://api.github.com/users/mcastelino","html_url":"https://github.com/mcastelino","followers_url":"https://api.github.com/users/mcastelino/followers","following_url":"https://api.github.com/users/mcastelino/following{/other_user}","gists_url":"https://api.github.com/users/mcastelino/gists{/gist_id}","starred_url":"https://api.github.com/users/mcastelino/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mcastelino/subscriptions","organizations_url":"https://api.github.com/users/mcastelino/orgs","repos_url":"https://api.github.com/users/mcastelino/repos","events_url":"https://api.github.com/users/mcastelino/events{/privacy}","received_events_url":"https://api.github.com/users/mcastelino/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-02-28T18:30:45Z","updated_at":"2017-02-28T18:30:45Z","closed_at":null,"body":"Currently containerd does not support the notion of a default runtime. Hence higher level orchestrators (such as swarm or cri) would need to specify the runtime that should be used when each container is created (and in the case of cri per POD)\r\n\r\nWe can either provide an option in containerd to allow for registration of a default runtime, or alternately require all higher level orchestrators to request a specific runtime per service/POD.\r\n\r\nHowever swarm today does not support sending in the runtime to be used at service creation time. It would be good to have that support in swarm such that the desired runtime be specifiable  at service creation time.\r\n\r\ncc @sameo"}}
{"actor":{"display_login":"mcastelino"}}