{"action":"closed","issue":{"url":"https://api.github.com/repos/jupyterhub/zero-to-jupyterhub-k8s/issues/690","repository_url":"https://api.github.com/repos/jupyterhub/zero-to-jupyterhub-k8s","labels_url":"https://api.github.com/repos/jupyterhub/zero-to-jupyterhub-k8s/issues/690/labels{/name}","comments_url":"https://api.github.com/repos/jupyterhub/zero-to-jupyterhub-k8s/issues/690/comments","events_url":"https://api.github.com/repos/jupyterhub/zero-to-jupyterhub-k8s/issues/690/events","html_url":"https://github.com/jupyterhub/zero-to-jupyterhub-k8s/issues/690","id":324645563,"node_id":"MDU6SXNzdWUzMjQ2NDU1NjM=","number":690,"title":"Emit a message when a Docker image is being pulled onto a node","user":{"login":"choldgraf","id":1839645,"node_id":"MDQ6VXNlcjE4Mzk2NDU=","avatar_url":"https://avatars1.githubusercontent.com/u/1839645?v=4","gravatar_id":"","url":"https://api.github.com/users/choldgraf","html_url":"https://github.com/choldgraf","followers_url":"https://api.github.com/users/choldgraf/followers","following_url":"https://api.github.com/users/choldgraf/following{/other_user}","gists_url":"https://api.github.com/users/choldgraf/gists{/gist_id}","starred_url":"https://api.github.com/users/choldgraf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/choldgraf/subscriptions","organizations_url":"https://api.github.com/users/choldgraf/orgs","repos_url":"https://api.github.com/users/choldgraf/repos","events_url":"https://api.github.com/users/choldgraf/events{/privacy}","received_events_url":"https://api.github.com/users/choldgraf/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2018-05-19T17:20:33Z","updated_at":"2018-07-21T15:44:23Z","closed_at":"2018-07-21T15:44:23Z","author_association":"MEMBER","body":"Sometimes it's good to know if a Docker image pull is happening. A good example is in BinderHub, where users don't understand why a session launch is taking much longer than normal (and it's usually because the pull operation takes a while to complete).\r\n\r\nOne way we could solve this is to have JupyterHub emit a message when a user session is launched for an image that doesn't currently exist on the node. BinderHub could then grab this message and display something to the user so they know it'll take longer than expected. I imagine administrators of JupyterHub also might find this useful as we start supporting cases where people launch a wider variety of Docker images from a JupyterHub deployment."}}
{"actor":{"display_login":"consideRatio"}}