Add a workaround for SageMaker Notebook Instance

Notebook Instances occasionally will not have the correct docker network bridge configured. Restarting the docker daemon will correct the configuration.

To detect whether we are on a SageMaker notebook, check if the SageMaker home directory exists.

Author: mckev-amazon

advanced_functionality/scikit_bring_your_own/scikit_bring_your_own.ipynb

@@ -267,6 +267,13 @@
     "\n",
     "# Build the docker image locally with the image name and then push it to ECR\n",
     "# with the full name.\n",
+    "\n",
+    "# On a SageMaker Notebook Instance, the docker daemon may need to be restarted in order\n",
+    "# to detect your network configuration correctly.  (This is a known issue.)\n",
+    "if [ -d \"/home/ec2-user/SageMaker\" ]; then\n",
+    "  sudo service docker restart\n",
+    "fi\n",
+    "\n",
     "docker build  -t ${algorithm_name} .\n",
     "docker tag ${algorithm_name} ${fullname}\n",
     "\n",