matthew/sonic-buildimage
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Update README.md (#17)

Browse Source 
Adjust the steps to make it clear everything is built inside builder container.
This commit is contained in:
Qi Luo 2016-09-28 17:23:22 -07:00 committed by lguohan
parent 7c0ff3e9e3
commit 9fe462fefc
1 changed files with 11 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
README.md
View File

@ -4,7 +4,17 @@
Build an [Open Network Install Environment (ONIE)](https://github.com/opencomputeproject/onie) compatiable network operating system (NOS) installer image for network switches, and also build docker images running inside the NOS.
# Prerequisite
## 1. Clone or fetch the code repository with all git submodules
## 1. Build environment
Build a docker image by [the Dockerfile](https://github.com/Azure/sonic-build-tools/blob/master/sonic-slave/Dockerfile) and build all remains in the docker container.
git clone https://github.com/Azure/sonic-build-tools
cd sonic-build-tools
./build.sh sonic-slave
docker run -v /var/run/docker.sock:/var/run/docker.sock -it local/sonic-slave bash
Note that all the below steps should be executed in the docker container, not in the host machine.
## 2. Clone or fetch the code repository with all git submodules
To clone the code repository recursively, assuming git version 1.9 or newer
git clone --recursive https://github.com/Azure/sonic-buildimage.git
@ -13,14 +23,6 @@ If it is already cloned, however there is no files under ./dockers/docker-base/
git submodule update --init --recursive
## 2. Build environment
Build a docker image by [the Dockerfile](https://github.com/Azure/sonic-build-tools/blob/master/sonic-slave/Dockerfile) and build all remains in the docker container.
git clone https://github.com/Azure/sonic-build-tools
cd sonic-build-tools
./build.sh sonic-slave
docker run -v /var/run/docker.sock:/var/run/docker.sock -it local/sonic-slave bash
## 3. Get vendor SAI SDK
Obtain Switch Abstraction Interface (SAI) SDK from one of supported vendors (see the list in [Usage](#usage) Section), and place it in the directory ./src/[VENDOR]-sdk/ as filelist.txt in that directory. Skip this step for p4 since it is an open source software switch.