Chromium Code Reviews Chromium Code Reviews
Issue 1638153002:
Set up an stunnel endpoint for the engine. (Closed)
Base URL: https://chromium.googlesource.com/chromium/src.git@master| OLD | NEW |
|---|---|
| 1 # Running the engine in a Docker container | 1 # Running the engine in a Docker container |
| 2 | 2 |
| 3 For local development and testing, you can run the engine in a Docker | 3 For local development and testing, you can run the engine in a Docker |
| 4 container. | 4 container. |
| 5 | 5 |
| 6 The steps are: | 6 The steps are: |
| 7 | 7 |
| 8 1. Bundle the engine and its dependencies. | 8 1. Bundle the engine and its dependencies. |
| 9 | 9 |
| 10 1. Build a Docker image. | 10 1. Build a Docker image. |
| (...skipping 69 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
| 80 | 80 |
| 81 If you need to map a directory into the Docker container (eg. for necessary | 81 If you need to map a directory into the Docker container (eg. for necessary |
| 82 files): | 82 files): |
| 83 | 83 |
| 84 ```bash | 84 ```bash |
| 85 docker run -v /path/to/srcdir:/path/to/docker/destdir blimp_engine | 85 docker run -v /path/to/srcdir:/path/to/docker/destdir blimp_engine |
| 86 ``` | 86 ``` |
| 87 | 87 |
| 88 NB: The permissions of the directory and the files outside of the Docker | 88 NB: The permissions of the directory and the files outside of the Docker |
| 89 container will be carried over into the container. | 89 container will be carried over into the container. |
| 90 | |
| 91 ### Mapping Ports for the Docker Container | |
|
maniscalco
2016/01/27 17:02:10
I think it might be time to revamp some of the doc
| |
| 92 | |
| 93 If you need to open a port for the Docker container in order to communicate: | |
| 94 | |
| 95 ```bash | |
| 96 docker run -p localport:dockerport blimp_engine | |
| 97 ``` | |
| OLD | NEW |
