docker-compose.yml: Prefer an unamed instance for now

Mostly because buildbox and thus the buildbox bot, used for sandboxed
builds, does not have named instance support...

#160

data/config/controller.conf

@@ -6,7 +6,7 @@ server:
 description: >
   Docker Compose controller configuration:
     - Unauthenticated plain HTTP at :50051
-    - Single instance: local
+    - Single instance: [unnamed]
     - Expects a remote CAS at :50052
     - Hosted services:
        - ActionCache
@@ -19,14 +19,14 @@ monitoring:
   enabled: false
 
 instances:
-  - name: local
+  - name: ''
     description: |
-      The unique 'local' instance.
+      The unique unnamed instance.
 
     storages:
       - !remote-storage &data-store
         url: http://storage:50052
-        instance-name: local
+        instance-name: ''
 
     services:
       - !action-cache &build-cache

data/config/storage.conf

@@ -6,7 +6,7 @@ server:
 description: >
   Docker Compose storage configuration:
     - Unauthenticated plain HTTP at :50052
-    - Single instance: local
+    - Single instance: [unnamed]
     - On-disk data stored in /var
     - Hosted services:
        - ContentAddressableStorage
@@ -19,9 +19,9 @@ monitoring:
   enabled: false
 
 instances:
-  - name: local
+  - name: ''
     description: |
-      The unique 'local' instance.
+      The unique unnamed instance.
 
     storages:
       - !disk-storage &data-store

docker-compose.yml

@@ -58,10 +58,16 @@ services:
   bots:  # To be scaled horizontaly
     image: buildgrid:local
     command: [
-      "bot", "--parent=local",
+      "bot", "--parent=",
       "--remote=http://controller:50051",
       "--remote-cas=http://storage:50052",
       "host-tools"]
+    #   "bot", "--parent=",
+    #   "--remote=http://controller:50051",
+    #   "--remote-cas=http://storage:50052",
+    #   "buildbox",
+    #   "--local-cas", "/var/lib/buildgrid/cache",
+    #   "--fuse-dir", "/mnt"]
     privileged: true
     volumes:
       - type: volume

docs/source/installation.rst

@@ -168,7 +168,7 @@ Once completed, you can start a minimal grid by running:
    - An execution and action-cache service available at
      ``http://localhost:50051``.
    - An CAS service available at ``http://localhost:50052``.
-   - A single ``local`` instance with one host-tools based worker bot attached.
+   - A single unnamed instance with one host-tools based worker bot attached.
 
 .. hint::