Merge pull request #4 from MicrosoftDocs/master

Updating to master

Author: Sagar-S-S

.openpublishing.redirection.json

@@ -0,0 +1,144 @@
+{
+    "$schema": "https://whatsnewapi.azurewebsites.net/schema",
+    "docSetProductName": "Visual Studio",
+    "rootDirectory": "docs/",
+    "docLinkSettings": {
+        "linkFormat": "relative",
+        "relativeLinkPrefix": "../"
+    },
+    "inclusionCriteria": {
+        "additionalMicrosoftOrgs": [
+            "ASP.NET"
+        ],
+        "labels": [
+            "-label:CLA"
+        ],
+        "minAdditionsToFile": 10
+    },
+    "areas": [
+        {
+            "name": "ai",
+            "heading": "AI"
+        },
+        {
+            "name": "azure",
+            "heading": "Azure"
+        },
+        {
+            "name": "code-quality",
+            "heading": "Code quality"
+        },
+        {
+            "name": "containers",
+            "heading": "Containers"
+        },
+        {
+            "name": "cross-platform",
+            "heading": "Cross platform"
+        },
+        {
+            "name": "data-tools",
+            "heading": "Data tools"
+        },
+        {
+            "name": "debugger",
+            "heading": "Debugger"
+        },
+        {
+            "name": "deployment",
+            "heading": "Deployment"
+        },
+        {
+            "name": "designers",
+            "heading": "Designers"
+        },
+        {
+            "name": "extensibility",
+            "heading": "Extensibility"
+        },
+        {
+            "name": "get-started",
+            "heading": "Get started"
+        },
+        {
+            "name": "help-viewer",
+            "heading": "Help viewer"
+        },
+        {
+            "name": "ide",
+            "heading": "IDE"
+        },
+        {
+            "name": "install",
+            "heading": "Install"
+        },
+        {
+            "name": "javascript",
+            "heading": "JavaScript"
+        },
+        {
+            "name": "media",
+            "heading": "Media"
+        },
+        {
+            "name": "misc",
+            "heading": "Misc"
+        },
+        {
+            "name": "modeling",
+            "heading": "Modeling"
+        },
+        {
+            "name": "msbuild",
+            "heading": "MSBuild"
+        },
+        {
+            "name": "porting",
+            "heading": "Porting"
+        },
+        {
+            "name": "profiling",
+            "heading": "Profiling"
+        },
+        {
+            "name": "python",
+            "heading": "Python"
+        },
+        {
+            "name": "rtvs",
+            "heading": "RTVS"
+        },
+        {
+            "name": "sharepoint",
+            "heading": "SharePoint"
+        },
+        {
+            "name": "test",
+            "heading": "Test"
+        },
+        {
+            "name": "vs-2015",
+            "heading": "VS 2015"
+        },
+        {
+            "name": "vsto",
+            "heading": "Vsto"
+        },
+        {
+            "name": "windows",
+            "heading": "Windows"
+        },
+        {
+            "name": "workflow-designer",
+            "heading": "Workflow designer"
+        },
+        {
+            "name": "xaml-tools",
+            "heading": "XAML tools"
+        },
+        {
+            "name": "xml-tools",
+            "heading": "XML tools"
+        }
+    ]
+}

.whatsnew.json

@@ -1,2 +1,35 @@
-- name: Index
-  href: index.md
+- name: Docker
+  expanded: true
+  items:
+  - name: Introduction to Docker for VS Code users 
+    expanded: true
+    items:
+    - name: "Getting started"
+      href: tutorials/docker-tutorial.md
+    - name: "Part 1: The application"
+      href: tutorials/your-application.md
+    - name: "Part 2: Update your app"
+      href: tutorials/update-your-app.md
+    - name: "Part 3: Share your app"
+      href: tutorials/share-your-app.md
+    - name: "Part 4: Persist your database"
+      href: tutorials/persist-your-data.md
+    - name: "Part 5: Use bind mounts"
+      href: tutorials/use-bind-mounts.md
+    - name: "Part 6: Multi-container apps"
+      href: tutorials/multi-container-apps.md
+    - name: "Part 7: Use Docker Compose"
+      href: tutorials/use-docker-compose.md
+    - name: "Part 8: Image-building best practices"
+      href: tutorials/image-building-best-practices.md
+    - name: "Part 9: Deploy to the cloud"
+      href: tutorials/deploy-to-cloud.md
+    - name: "What's next?"
+      href: tutorials/whats-next.md
+
+    - name: Sources
+      items:
+      - name: Examples
+        href: https://github.com/docker/awesome-compose
+      - name: Docker ACI integration 
+        href: https://github.com/docker/aci-integration-beta/

docker/TOC.yml

@@ -39,9 +39,16 @@
     "overwrite": [],
     "externalReference": [],
     "globalMetadata": {
+      "feedback_system": "GitHub",
+      "feedback_github_repo": "MicrosoftDocs/visualstudio-docs",
       "breadcrumb_path": "/visualstudio/docker/breadcrumb/toc.json",
       "extendBreadcrumb": true,
-      "feedback_system": "None"
+      "ms.prod": "visual-studio-windows",
+      "manager": "jillfra",
+      "author": "jillre",
+      "ms.author": "jillfra",
+      "ms.topic": "conceptual",
+      "audience": "developer"
     },
     "fileMetadata": {},
     "template": [],

docker/docfx.json

@@ -0,0 +1,85 @@
+---
+title: "Docker tutorial - Part 9: Deploy to the cloud"
+description: Deploy a docker app to a cloud service for hosting.
+ms.date: "08/04/2020"
+author: nebuk89
+ms.author: ghogen
+manager: jillfra
+ms.technology: vs-azure
+ms.topic: conceptual
+ms.workload:
+  - "azure"
+---
+# Deploy to the cloud
+
+Now that you have run your app locally, you can start to think about running it in the cloud so other people can access it and make use of it. To do this, you'll use Docker contexts. A context is the place where you're currently working with containers. Right now, you only have your "default" context, so you'll need to add a cloud one and deploy your app to it.
+
+## Create your cloud context
+
+1. To start, you can see what contexts you have by looking at the contexts section of the Docker panel:
+
+   ![Shows only default context](media/defaultcontext.png)
+
+You should only see your default context for local work.
+
+1. To deploy to the cloud, you need to create a new ACI context, but to do this, you first need the Azure account extension to authenticate with Azure.
+
+   ![Adding Azure extension](media/addazureextension.png)
+
+You'll need to set up an Azure account if you don’t already have one.
+
+1. Now you can create your new ACI context. You can do this by clicking the plus button on the **Contexts** section of the Docker view.
+
+   ![Creating your ACI context](media/createnewcontext.png)
+
+This will ask you what resource group you want to run these containers under. Either select an existing group using the arrow keys, or use the default option to use the new group.
+
+![Selecting your resource group](media/selectresourcegroup.png)
+
+You can now see your ACI context listed and can right-click it to make it your current focus/in use context:
+
+![New ACI context can be selected](media/listofcontexts.png)
+
+## Run containers in the cloud
+
+1. Now, use your ACI context and run the container.
+
+   ```bash
+   docker context use myacicontext
+   docker run  -dp 3000:3000 <username>/getting-started
+   ```
+
+1. Having run this, now look at the container in your context.
+
+   ![Container running in your ACI context](media/contextcontainer.png)
+
+1. To check this is all working properly, you can right-click on the running container and choose **View in browser**.
+
+   ![Container in ACI with public IP](media/containerinaci.png)
+
+And, you can see that the container is running in a public IP and working correctly!
+
+1. Now, you can have a look at our running container to see how it is working. You can start by having a look at the container logs:
+ 
+ ```bash
+   docker logs distracted-jackson
+   ```
+
+1. You can also exec into your container as you would with a local container.
+ 
+ ```bash
+   docker exec -it distracted-jackson sh
+   ```
+
+1. Lastly to clean up your working space and to make sure you're not being charged for continuing to run the test container, you can simply right-click on the running container and choose **Remove**.
+
+## Recap
+
+Fantastic, you've now taken your workload and deployed it to the cloud successfully for the first time. You can do all of this from the command line as well from within your ACI context using `docker run` and also using `docker compose up` to run your multi-container applications. To find out more about running your containers in the cloud, read through the extended [documentation on using ACI](https://docs.docker.com/engine/context/aci-integration/).
+
+## Next steps
+
+Continue with the tutorial!
+
+> [!div class="nextstepaction"]
+> [What's next](whats-next.md)

docker/index.md

@@ -0,0 +1,74 @@
+---
+title: "Docker tutorial - Get started with Docker"
+description: A multi-step tutorial that covers the basics of working with Docker with Visual Studio Code.
+ms.date: "08/04/2020"
+author: nebuk89
+ms.author: ghogen
+manager: jillfra
+ms.technology: vs-azure
+ms.topic: conceptual
+ms.workload:
+  - "azure"
+next_page: app.md
+---
+
+# Tutorial: Get started with Docker
+
+In this tutorial, you'll learn about creating and deploying Docker apps, including using multiple containers with a database, and using Docker Compose. You'll also deploy your containerized app to Azure.
+
+## Start the tutorial
+
+If you've already run the command to get started with the tutorial, congratulations!  If not, open a command prompt or bash window, and run the command:
+
+```cli
+docker run -d -p 80:80 docker/getting-started
+```
+
+You'll notice a few flags being used. Here's some more info on them:
+
+- `-d` - run the container in detached mode (in the background)
+- `-p 80:80` - map port 80 of the host to port 80 in the container
+- `docker/getting-started` - the image to use
+
+> [!TIP]
+> You can combine single character flags to shorten the full command.
+> As an example, the command above could be written as:
+>
+> ```cli
+> docker run -dp 80:80 docker/getting-started
+> ```
+
+## The VS Code Extension
+
+Before going too far, we want to highlight the Docker VS Code Extension, which gives you a quick view of the containers running on your machine. It gives you quick
+access to container logs, lets you get a shell inside the container, and lets you easily manage container lifecycle (stop, remove, and so on).
+
+To access the extension, follow the instructions [here](https://code.visualstudio.com/docs/containers/overview). Use the Docker icon on the left to open the Docker view. If you open the extension now, you will see this tutorial running! The container name (`angry_taussig` below) is a randomly created name. So, you'll most likely have a different name.
+
+![Tutorial container running in Docker Extension](media/vs-tutorial-in-extension.png)
+
+## What is a container
+
+Now that you've run a container, what *is* a container? Simply put, a container is simply another process on your machine that has been isolated from all other processes on the host machine. That isolation leverages [kernel namespaces and cgroups](https://medium.com/@saschagrunert/demystifying-containers-part-i-kernel-space-2c53d6979504), features that have been in Linux for a long time. Docker has worked to make these capabilities approachable and easy to use.
+
+> [!NOTE]
+> **Creating Containers from Scratch**
+> If you'd like to see how containers are built from scratch, Liz Rice from Aqua Security has a video in which she creates a container from scratch in Go:
+>
+> [!VIDEO https://www.youtube-nocookie.com/embed/8fi7uSYlOdc]
+
+## What is a container image
+
+When running a container, it uses an isolated filesystem. This custom filesystem is provided by a **container image**. Since the image contains the container's filesystem, it must contain everything needed to run an application - all dependencies, configuration, scripts, binaries, and so on. The image also contains other configuration for the container, such as environment variables, a default command to run, and other metadata.
+
+We'll dive deeper into images later on, covering topics such as layering, best practices, and more.
+
+> [!NOTE]
+> If you're familiar with `chroot`, think of a container as an extended version of `chroot`. The filesystem is simply coming from the image. But, a container adds additional isolation not available when simply using chroot.
+
+## Next steps
+
+Continue with the tutorial!
+
+> [!div class="nextstepaction"]
+> [The application](your-application.md)