Docker-Image.md

@@ -44,7 +44,7 @@ The material in this document requires the use of [Docker](https://www.docker.co
 
 Docker images contain all of the files and binaries needed to run a particular task. You can think of Docker images as virtual machine snapshots. Our container registry has a collection of these images. Much like Git, these _tags_ are images that contain different files for different projects. We'll pull the `latest` tag, as shown below:
 
-```
+```bash
 docker pull socks.lbl.gov:4567/cag/bxe/firesim
 ```
 
@@ -56,13 +56,15 @@ Once you've pulled a Docker image, you can run within a container. You can think
 
 - Running a Docker container interactively
   - This runs the Docker container and attaches the console of your container
-  ```
+
+  ```bash
   docker run [--privileged] [--name CUSTOM_CONTAINER_NAME] -it socks.lbl.gov:4567/cag/bxe/firesim
   ```
 
 - Running a Docker container and attaching later
   - You can run a Docker container in the background and attach to it
-  ```
+  
+  ```bash
   docker run [--privileged] [--name CUSTOM_CONTAINER_NAME] socks.lbl.gov:4567/cag/bxe/firesim
   docker attach [HASHID/STRINGID/CUSTOM_CONTAINER_NAME]
   ```
@@ -71,7 +73,7 @@ Once you've pulled a Docker image, you can run within a container. You can think
 
 You can mount directories from your host machine within your container with the `-v [HOSTDIR]:[CONTAINERDIR]` flag. In this example, we want to mount `/tmp/mpoint` from our host machine to `/app` in the container.
 
-```
+```bash
 docker run \
     [--privileged] [--name CUSTOM_CONTAINER_NAME] \
     -it \
@@ -85,7 +87,7 @@ Any changes made in `/app` in the Docker container are reflected in `/tmp/mpoint
 
 Once you've run and attached to your Docker container, you should see the following output on your console:
 
-```
+```bash
 (base) root@[HASHID]:~/firesim$
 ```