{
  "id": 153971,
  "title": "What's the meaning of this error after ~4 hours of GPU training?",
  "url": "/competitions/global-wheat-detection/discussion/153971",
  "author_name": "",
  "post_date": "2020-05-26T16:59:11.564693600Z",
  "votes": 5,
  "comment_count": 1,
  "views": 0,
  "content": "<p>I got following error after training my model for 5 hours on GPU: \n&gt; Cannot connect to the Docker daemon at tcp://172.21.64.14:2375. Is the docker daemon running?</p>\n\n<p>Here is the screenshot of the error log:\n<img src=\"https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F1905996%2Fa28fee8bc54935d0e7392340e3156371%2FScreenshot%202020-05-26%20at%2010.28.32%20PM.png?generation=1590512339809561&amp;alt=media\" alt=\"\"></p>",
  "messages": [
    {
      "id": "862566",
      "postDate": "05/26/2020 16:59:11",
      "content": "<p>I got following error after training my model for 5 hours on GPU: \n&gt; Cannot connect to the Docker daemon at tcp://172.21.64.14:2375. Is the docker daemon running?</p>\n\n<p>Here is the screenshot of the error log:\n<img src=\"https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F1905996%2Fa28fee8bc54935d0e7392340e3156371%2FScreenshot%202020-05-26%20at%2010.28.32%20PM.png?generation=1590512339809561&amp;alt=media\" alt=\"\"></p>",
      "rawMarkdown": "I got following error after training my model for 5 hours on GPU: \n&gt; Cannot connect to the Docker daemon at tcp://172.21.64.14:2375. Is the docker daemon running?\n\nHere is the screenshot of the error log:\n![](https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F1905996%2Fa28fee8bc54935d0e7392340e3156371%2FScreenshot%202020-05-26%20at%2010.28.32%20PM.png?generation=1590512339809561&amp;alt=media)",
      "votes": null
    },
    {
      "id": "931034",
      "postDate": "07/15/2020 23:02:17",
      "content": "<p><a href=\"/kaushal2896\">@kaushal2896</a> Sorry this affected you. This happens around 0.01% of the time, usually because the machine running your notebook was taken down for maintenance we had no control over. At some point in the future this will improve, and I keep bugging the team running that effort for when they'll fix it.</p>\n\n<p>The solution is just to try again, the chances you hit it again should be very unlikely.</p>",
      "rawMarkdown": "kaushal2896 Sorry this affected you. This happens around 0.01% of the time, usually because the machine running your notebook was taken down for maintenance we had no control over. At some point in the future this will improve, and I keep bugging the team running that effort for when they'll fix it.\n\nThe solution is just to try again, the chances you hit it again should be very unlikely.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 931034,
      "author_name": "herbison",
      "author_url": "",
      "post_date": "07/15/2020 23:02:17",
      "content": "<p><a href=\"/kaushal2896\">@kaushal2896</a> Sorry this affected you. This happens around 0.01% of the time, usually because the machine running your notebook was taken down for maintenance we had no control over. At some point in the future this will improve, and I keep bugging the team running that effort for when they'll fix it.</p>\n\n<p>The solution is just to try again, the chances you hit it again should be very unlikely.</p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "862566": "I got following error after training my model for 5 hours on GPU: \n&gt; Cannot connect to the Docker daemon at tcp://172.21.64.14:2375. Is the docker daemon running?\n\nHere is the screenshot of the error log:\n![](https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F1905996%2Fa28fee8bc54935d0e7392340e3156371%2FScreenshot%202020-05-26%20at%2010.28.32%20PM.png?generation=1590512339809561&amp;alt=media)",
    "931034": "kaushal2896 Sorry this affected you. This happens around 0.01% of the time, usually because the machine running your notebook was taken down for maintenance we had no control over. At some point in the future this will improve, and I keep bugging the team running that effort for when they'll fix it.\n\nThe solution is just to try again, the chances you hit it again should be very unlikely."
  },
  "source": "meta"
}