Skip to content

Commit c1364de

Browse files
committed
Updates to docker steps
1 parent 2ad41d4 commit c1364de

File tree

3 files changed

+29
-1
lines changed

3 files changed

+29
-1
lines changed

orfs-build.md

Lines changed: 26 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,9 +79,34 @@ Docker.builder docker image gets built from DockerHelper.sh, but that doesn't ta
7979
### Using OpenROAD in Docker
8080

8181
This is very similar to the ORFS docker image that you used in the [walkthrough](/orfs-walkthrough.md)
82-
except that you need to specify a local docker image and tag:
82+
except that you need to specify a local docker image and tag that are shown in the final steps of your compilation:
83+
84+
```
85+
#25 naming to docker.io/openroad/flow-ubuntu22.04-builder:6cd62b
86+
```
87+
88+
I make a modified version of the ```runorfs.sh``` script (called ```runme.sh```) that uses this image and a general tag:
89+
90+
```bash
91+
#!/bin/bash
92+
#
93+
TAG="${1:-latest}"
94+
echo "Running OpenROAD flow with tag: ${TAG}"
95+
docker run --rm -it \
96+
-u $(id -u ${USER}):$(id -g ${USER}) \
97+
-v $(pwd)/flow:/OpenROAD-flow-scripts/flow \
98+
-e DISPLAY=${DISPLAY} \
99+
-v /tmp/.X11-unix:/tmp/.X11-unix \
100+
-v ${HOME}/.Xauthority:/.Xauthority \
101+
--network host \
102+
--security-opt seccomp=unconfined \
103+
docker.io/openroad/flow-ubuntu22.04-builder:${TAG}
104+
```
105+
106+
Specify th tag to run this version:
83107

84108
```bash
109+
./runme.sh 6cd62b
85110
```
86111

87112
## Local

orfs-walkthrough.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,9 @@ This assumes that the smoke test runs and you've [installed ORFS properly](orfs-
66

77
The documentation is available at [ReadTheDocs](https://openroad.readthedocs.io/en/latest/).
88

9+
The general steps of ORFS are shown here:
10+
![OpenROAD Flow Scripts Methodology Steps](orfs/orfs_flow.png)
11+
912
ORFS uses a Makefile to run the flow scripts. Specifically, it goes through the following steps that you see in the output
1013
of a successful run:
1114

orfs/orfs_flow.png

104 KB
Loading

0 commit comments

Comments
 (0)