{"action":"created","issue":{"url":"https://api.github.com/repos/docker/docker/issues/10682","labels_url":"https://api.github.com/repos/docker/docker/issues/10682/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/10682/comments","events_url":"https://api.github.com/repos/docker/docker/issues/10682/events","html_url":"https://github.com/docker/docker/pull/10682","id":57207655,"number":10682,"title":"Proposal: Add a NOCACHE instruction to Dockerfiles","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":[{"url":"https://api.github.com/repos/docker/docker/labels/status/2-needs-code-review","name":"status/2-needs-code-review","color":"fad8c7"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":65,"created_at":"2015-02-10T17:32:51Z","updated_at":"2015-04-16T15:17:58Z","closed_at":"2015-04-15T23:03:16Z","pull_request":{"url":"https://api.github.com/repos/docker/docker/pulls/10682","html_url":"https://github.com/docker/docker/pull/10682","diff_url":"https://github.com/docker/docker/pull/10682.diff","patch_url":"https://github.com/docker/docker/pull/10682.patch"},"body":"This adds a NOCACHE instruction to Dockerfiles which will disable all\r\ncaching from that point forward.  The cache is still populated, but the\r\nlook-up processing is disbled.\r\n\r\nCloses #1996\r\n\r\nSigned-off-by: Doug Davis <dug@us.ibm.com>"},"comment":{"url":"https://api.github.com/repos/docker/docker/issues/comments/93761068","html_url":"https://github.com/docker/docker/pull/10682#issuecomment-93761068","issue_url":"https://api.github.com/repos/docker/docker/issues/10682","id":93761068,"user":{"login":"jfrazelle","id":1445228,"avatar_url":"https://avatars.githubusercontent.com/u/1445228?v=3","gravatar_id":"","url":"https://api.github.com/users/jfrazelle","html_url":"https://github.com/jfrazelle","followers_url":"https://api.github.com/users/jfrazelle/followers","following_url":"https://api.github.com/users/jfrazelle/following{/other_user}","gists_url":"https://api.github.com/users/jfrazelle/gists{/gist_id}","starred_url":"https://api.github.com/users/jfrazelle/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jfrazelle/subscriptions","organizations_url":"https://api.github.com/users/jfrazelle/orgs","repos_url":"https://api.github.com/users/jfrazelle/repos","events_url":"https://api.github.com/users/jfrazelle/events{/privacy}","received_events_url":"https://api.github.com/users/jfrazelle/received_events","type":"User","site_admin":false},"created_at":"2015-04-16T15:17:58Z","updated_at":"2015-04-16T15:17:58Z","body":"I was referring to the examples in this comment\nhttps://github.com/docker/docker/pull/10682#issuecomment-73774066\n\nAlso to delve even deeper into why I do not think this is necessary\nQuoting from another comment by @tianon (\nhttps://github.com/docker/docker/pull/10682#issuecomment-73936132):\n> IMO, the cache isn't a feature a Dockerfile author should be counting on\n-- it's a convenience provided to speed up subsequent builds.\n\nI strongly agree with that statement, what you are asking for is the\nequivalent of a \"git rebase\" of your docker file cache to be called at will\nand whenever the user sees necessary, we are not git, this is way over the\ncomplication that we need. We can keep things simple and have appropriate\ncache busts with the examples Tianon provided. We do not need to rewrite\ngit like features into the builder when in reality the builder should\nreally not do anything and just rely entirely on shell (but that's going\nsuper deep into my opinion on this).\n\nOn Thursday, April 16, 2015, Doug Davis <notifications@github.com> wrote:\n\n> @jfrazelle <https://github.com/jfrazelle> @icecrime\n> <https://github.com/icecrime> can one of you enumerate the recommended\n> approach(s) to solve the usecases this PR was trying toaddress? I really\n> think adding something to the \"User's Guide\" would be really valuable here,\n> but I'm not clear on what the recommended answer is - and w/o that I can't\n> create a doc PR.\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/docker/docker/pull/10682#issuecomment-93738328>.\n>\n"}}