{"action":"created","issue":{"url":"https://api.github.com/repos/docker/docker/issues/10773","labels_url":"https://api.github.com/repos/docker/docker/issues/10773/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/10773/comments","events_url":"https://api.github.com/repos/docker/docker/issues/10773/events","html_url":"https://github.com/docker/docker/issues/10773","id":57637873,"number":10773,"title":"docker inspect with an image instead of a container logs errors (trivial)","user":{"login":"burke","id":1284,"avatar_url":"https://avatars.githubusercontent.com/u/1284?v=3","gravatar_id":"","url":"https://api.github.com/users/burke","html_url":"https://github.com/burke","followers_url":"https://api.github.com/users/burke/followers","following_url":"https://api.github.com/users/burke/following{/other_user}","gists_url":"https://api.github.com/users/burke/gists{/gist_id}","starred_url":"https://api.github.com/users/burke/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/burke/subscriptions","organizations_url":"https://api.github.com/users/burke/orgs","repos_url":"https://api.github.com/users/burke/repos","events_url":"https://api.github.com/users/burke/events{/privacy}","received_events_url":"https://api.github.com/users/burke/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-02-13T18:48:16Z","updated_at":"2015-05-27T11:24:00Z","closed_at":null,"body":"From a script, I've called `docker inspect ${my_image}`. Everything works as expected, but docker logs a couple \"error\" lines when it first fails to look up my image as a container, before proceeding to look it up as an image.\r\n\r\nIt should probably only be logging an error if both lookups fail.\r\n\r\n```\r\nINFO[5635] -job container_inspect(registry.chi.shopify.io:80/shopify:0beb47b3f04357bf6a4dfb25784d591fa0358a02) = ERR (1)\r\nERRO[5635] Handler for GET /containers/{name:.*}/json returned error: No such container: registry.chi.shopify.io:80/shopify:0beb47b3f04357bf6a4dfb25784d591fa0358a02\r\nERRO[5635] HTTP Error: statusCode=404 No such container: registry.chi.shopify.io:80/shopify:0beb47b3f04357bf6a4dfb25784d591fa0358a02\r\nINFO[5635] GET /v1.17/images/registry.chi.shopify.io:80/shopify:0beb47b3f04357bf6a4dfb25784d591fa0358a02/json\r\nINFO[5635] +job image_inspect(registry.chi.shopify.io:80/shopify:0beb47b3f04357bf6a4dfb25784d591fa0358a02)\r\n```"},"comment":{"url":"https://api.github.com/repos/docker/docker/issues/comments/105875168","html_url":"https://github.com/docker/docker/issues/10773#issuecomment-105875168","issue_url":"https://api.github.com/repos/docker/docker/issues/10773","id":105875168,"user":{"login":"phemmer","id":1826947,"avatar_url":"https://avatars.githubusercontent.com/u/1826947?v=3","gravatar_id":"","url":"https://api.github.com/users/phemmer","html_url":"https://github.com/phemmer","followers_url":"https://api.github.com/users/phemmer/followers","following_url":"https://api.github.com/users/phemmer/following{/other_user}","gists_url":"https://api.github.com/users/phemmer/gists{/gist_id}","starred_url":"https://api.github.com/users/phemmer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/phemmer/subscriptions","organizations_url":"https://api.github.com/users/phemmer/orgs","repos_url":"https://api.github.com/users/phemmer/repos","events_url":"https://api.github.com/users/phemmer/events{/privacy}","received_events_url":"https://api.github.com/users/phemmer/received_events","type":"User","site_admin":false},"created_at":"2015-05-27T11:24:00Z","updated_at":"2015-05-27T11:24:00Z","body":"Just chiming in here, but in my opinion, the solution is to drop these down from `error` level to something else, like `info`.\r\n\r\nThe `error` level is commonly used to indicate an issue within the application (https://stackoverflow.com/questions/2031163/when-to-use-log-level-warn-vs-error). These failed requests are not an issue with the docker daemon, but rather a bad request from the client. Thus they should not be logged as errors."}}