One may build ``nncc`` docker image with the following command:
```
-nncc$ cat Dockerfile | docker build -t nncc -
+nncc$ cat infra/nncc/Dockerfile | docker build -t nncc -
...
```
By default, this ``Dockerfile`` uses "archive.ubuntu.com" which may be quite slow. One may use mirror site via ``UBUNTU_MIRROR`` variable.
For example, one may enable the use of ``kr.archive.ubuntu.com`` via the following command
```
-nncc$ cat Dockerfile | docker build --build-arg UBUNTU_MIRROR="kr.archive.ubuntu.com" -t nncc -
+nncc$ cat infra/nncc/Dockerfile | docker build --build-arg UBUNTU_MIRROR="kr.archive.ubuntu.com" -t nncc -
...
```
One who works behind proxy should provide proxy configuration via the following command:
```
-nncc$ cat Dockerfile | docker build --build-arg HTTP_PROXY=<HTTP proxy address> --build-arg HTTPS_PROXY=<HTTPS proxy address> -t nncc -
+nncc$ cat infra/nncc/Dockerfile | docker build --build-arg HTTP_PROXY=<HTTP proxy address> --build-arg HTTPS_PROXY=<HTTPS proxy address> -t nncc -
...
```
One may use simplified command if ``HTTP_PROXY`` and ``HTTPS_PROXY`` environment variables are already set:
declare -x HTTP_PROXY=...
declare -x HTTPS_PROXY=...
...
-nncc$ cat Dockerfile | docker build --build-arg HTTP_PROXY --build-arg HTTPS_PROXY -t nncc -
+nncc$ cat infra/nncc/Dockerfile | docker build --build-arg HTTP_PROXY --build-arg HTTPS_PROXY -t nncc -
...
```
Note that these configurations are orthogonal to each other. One may freely combine these options as follows:
```
-nncc$ cat Dockerfile | docker build --build-arg HTTP_PROXY --build-arg HTTPS_PROXY --build-arg UBUNTU_MIRROR="kr.archive.ubuntu.com" -t nncc -
+nncc$ cat infra/nncc/Dockerfile | docker build --build-arg HTTP_PROXY --build-arg HTTPS_PROXY --build-arg UBUNTU_MIRROR="kr.archive.ubuntu.com" -t nncc -
```
One may easily build _nncc_ with the following command once ``nncc`` docker image is built.