Index: blimp/docs/container.md |
diff --git a/blimp/docs/container.md b/blimp/docs/container.md |
index 31adc802ee2b6fc603aa6d3c1703468b7d67804d..7a1902a742986b4d30db41cbf1098699325013a2 100644 |
--- a/blimp/docs/container.md |
+++ b/blimp/docs/container.md |
@@ -43,7 +43,7 @@ dependencies. From time to time, this list may need to be updated. Use |
```bash |
./blimp/tools/generate-engine-manifest.py \ |
- --build-dir out-linux/Debug \ |
+ --build-dir out-chromeos/Debug \ |
--target //blimp/engine:blimp_engine \ |
--output blimp/engine/engine-manifest.txt |
``` |
@@ -56,7 +56,7 @@ dependencies. |
Using the tarfile you can create a Docker image: |
```bash |
-docker build -t blimp_engine - < ./out-linux/Debug/blimp_engine_bundle.tar |
+docker build -t blimp_engine - < ./out-chromeos/Debug/blimp_engine_bundle.tar.gz |
``` |
## Running the Engine in a Docker Container |
@@ -74,7 +74,8 @@ few files that are not provided by the container. You need: |
public certificate. Permissions should be set to 644. |
* `$CONFIG_DIR/client_token`: A file with a non-empty string used as the |
client token (the shared secret between the client and the engine). |
- Persmissions should also be set to 644. |
+ Permissions should also be set to 644. See [running](running.md) for how |
+ to get the default token from the source code. |
This setup step is only required once and can be reused for all the rest of the |
runs of the engine. |
@@ -94,4 +95,3 @@ docker run ... blimp_engine --with-my-flags |
``` |
See the [blimp engine `Dockerfile`](../engine/Dockerfile) to find out what flags |
are passed by default. |
- |