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
 ```
 
@@ -56,13 +56,13 @@ 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
   ```
 
 - 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
   docker attach [HASHID/STRINGID/CUSTOM_CONTAINER_NAME]
   ```
@@ -71,7 +71,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 \
@@ -79,6 +79,33 @@ docker run \
     socks.lbl.gov:4567/cag/bxe
 ```
 
+# Initializing the Chipyard and FireMarshal Environment
+
+Once you've run and attached to your Docker container, you should see the following output on your console:
+
+```
+(base) root@[HASHID]:~/firesim#
+```
+
+Run the following command to set up the Chipyard and FireMarshal environment:
+
+```bash
+source source-env.sh
+```
+
+You should see the following output on your console:
+
+```
+(base) root@[HASHID]:~/firesim# source source-env.sh 
+Activating FireSim Conda Environment...
+Sourcing FireSim Environment...
+Navigating to Chipyard Directory...
+Sourcing Chipyard Environment...
+(/root/firesim/target-design/chipyard/.conda-env) root@[HASHID]:~/firesim/target-design/chipyard#
+```
+
+You are now ready to build RTL with Chipyard and build software with FireMarshal.
+
 ---
 
 [^1]: This research is based upon work supported by the Office of the Director of National Intelligence (ODNI), Intelligence Advanced Research Projects Activity (IARPA), through the Advanced Graphical Intelligence Logical Computing Environment (AGILE) research program, under Army Research Office (ARO) contract number D2021-2106030006. The views and conclusions contained herein are those of the authors and should not be interpreted as necessarily representing the official policies or endorsements, either expressed or implied, of the ODNI, IARPA, ARO, or the U.S.  Government.