{"action":"created","issue":{"url":"https://api.github.com/repos/docker/compose/issues/1458","labels_url":"https://api.github.com/repos/docker/compose/issues/1458/labels{/name}","comments_url":"https://api.github.com/repos/docker/compose/issues/1458/comments","events_url":"https://api.github.com/repos/docker/compose/issues/1458/events","html_url":"https://github.com/docker/compose/issues/1458","id":80690820,"number":1458,"title":"Up does not honor timeout","user":{"login":"thieman","id":1414305,"avatar_url":"https://avatars.githubusercontent.com/u/1414305?v=3","gravatar_id":"","url":"https://api.github.com/users/thieman","html_url":"https://github.com/thieman","followers_url":"https://api.github.com/users/thieman/followers","following_url":"https://api.github.com/users/thieman/following{/other_user}","gists_url":"https://api.github.com/users/thieman/gists{/gist_id}","starred_url":"https://api.github.com/users/thieman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thieman/subscriptions","organizations_url":"https://api.github.com/users/thieman/orgs","repos_url":"https://api.github.com/users/thieman/repos","events_url":"https://api.github.com/users/thieman/events{/privacy}","received_events_url":"https://api.github.com/users/thieman/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-05-25T22:32:53Z","updated_at":"2015-05-26T10:28:30Z","closed_at":"2015-05-26T10:28:30Z","body":"`docker-compose up --help` promises a `timeout` option that appears to do absolutely nothing. Compose takes the standard 10 seconds to stop the running containers when I run the `up` command with my containers already started, regardless of what I pass here.\r\n\r\n```\r\n> docker-compose up --help\r\n    -t, --timeout TIMEOUT  When attached, use this timeout in seconds\r\n                           for the shutdown. (default: 10)\r\n```\r\n\r\nThe timeout is also broken for `restart` in 1.2, though this has since been fixed: https://github.com/docker/compose/issues/1311. There seems to be a larger systemic issue of the docstrings not actually being tied to CLI functionality, which results in showing misleading information to end users and is extremely frustrating. Would be great to see this addressed."},"comment":{"url":"https://api.github.com/repos/docker/compose/issues/comments/105482500","html_url":"https://github.com/docker/compose/issues/1458#issuecomment-105482500","issue_url":"https://api.github.com/repos/docker/compose/issues/1458","id":105482500,"user":{"login":"aanand","id":1062,"avatar_url":"https://avatars.githubusercontent.com/u/1062?v=3","gravatar_id":"","url":"https://api.github.com/users/aanand","html_url":"https://github.com/aanand","followers_url":"https://api.github.com/users/aanand/followers","following_url":"https://api.github.com/users/aanand/following{/other_user}","gists_url":"https://api.github.com/users/aanand/gists{/gist_id}","starred_url":"https://api.github.com/users/aanand/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aanand/subscriptions","organizations_url":"https://api.github.com/users/aanand/orgs","repos_url":"https://api.github.com/users/aanand/repos","events_url":"https://api.github.com/users/aanand/events{/privacy}","received_events_url":"https://api.github.com/users/aanand/received_events","type":"User","site_admin":false},"created_at":"2015-05-26T10:28:30Z","updated_at":"2015-05-26T10:28:30Z","body":"Yes, that's where the timeout applies. Feel free to open a feature request as you describe.\r\n\r\n> There seems to be a larger systemic issue of the docstrings not actually being tied to CLI functionality, which results in showing misleading information to end users and is extremely frustrating.\r\n\r\nBecause we use [docopt](http://docopt.org/), the CLI functionality is derived directly *from* the docstrings, so there's little chance of that."}}