{"action":"created","issue":{"url":"https://api.github.com/repos/opencontainers/runc/issues/310","labels_url":"https://api.github.com/repos/opencontainers/runc/issues/310/labels{/name}","comments_url":"https://api.github.com/repos/opencontainers/runc/issues/310/comments","events_url":"https://api.github.com/repos/opencontainers/runc/issues/310/events","html_url":"https://github.com/opencontainers/runc/issues/310","id":109518571,"number":310,"title":"specifying a spec file on cmd line?","user":{"login":"duglin","id":1944671,"avatar_url":"https://avatars.githubusercontent.com/u/1944671?v=3","gravatar_id":"","url":"https://api.github.com/users/duglin","html_url":"https://github.com/duglin","followers_url":"https://api.github.com/users/duglin/followers","following_url":"https://api.github.com/users/duglin/following{/other_user}","gists_url":"https://api.github.com/users/duglin/gists{/gist_id}","starred_url":"https://api.github.com/users/duglin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/duglin/subscriptions","organizations_url":"https://api.github.com/users/duglin/orgs","repos_url":"https://api.github.com/users/duglin/repos","events_url":"https://api.github.com/users/duglin/events{/privacy}","received_events_url":"https://api.github.com/users/duglin/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-10-02T15:47:33Z","updated_at":"2015-10-02T17:16:43Z","closed_at":null,"body":"Per the OCF spec, the config file must be named `config.json` so its a bit odd that we allow people to specify a different name on the runc command line. I'm not sure a reference implementation should allow for deviations from the spec like this. I think it might make more sense to allow for the user to pass in the location of the bundle dir, in which are the config files and rootfs dirs though.\r\n\r\nI'd be happy to open a PR for these but I wanted to see what people thought first."},"comment":{"url":"https://api.github.com/repos/opencontainers/runc/issues/comments/145089866","html_url":"https://github.com/opencontainers/runc/issues/310#issuecomment-145089866","issue_url":"https://api.github.com/repos/opencontainers/runc/issues/310","id":145089866,"user":{"login":"duglin","id":1944671,"avatar_url":"https://avatars.githubusercontent.com/u/1944671?v=3","gravatar_id":"","url":"https://api.github.com/users/duglin","html_url":"https://github.com/duglin","followers_url":"https://api.github.com/users/duglin/followers","following_url":"https://api.github.com/users/duglin/following{/other_user}","gists_url":"https://api.github.com/users/duglin/gists{/gist_id}","starred_url":"https://api.github.com/users/duglin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/duglin/subscriptions","organizations_url":"https://api.github.com/users/duglin/orgs","repos_url":"https://api.github.com/users/duglin/repos","events_url":"https://api.github.com/users/duglin/events{/privacy}","received_events_url":"https://api.github.com/users/duglin/received_events","type":"User","site_admin":false},"created_at":"2015-10-02T17:16:43Z","updated_at":"2015-10-02T17:16:43Z","body":"The problem with allowing other variants in runc is that you are headed down the path of standardizing an extension and unless runc takes the \"other\" config.json (either from a different file or from stdin) and generates a config.json in the bundle dir, I think its fair to say that its running a non-compliant bundle and doing something in violation of the spec.\r\n\r\nOr, put it another way, I think 'runc' as a reference implementation should enforce each \"MUST\" we see in the spec, and right now we say there MUST be a config.json and runconfig.json in the root of the bundle dir - how it gets there could be up an impl detail of runc, but in the end if the spec says it MUST be there, then runc needs to follow that rule."}}