Avoid docker-compose

The way it handles docker networks breaks builds.

MANIFEST.in

@@ -1,6 +1,5 @@
 # setuptools-scm includes everything tracked by git
 prune docker
-prune docker-compose
 prune scripts
 prune tests/storage/servers
 prune tests/storage/etesync

docker-compose.yaml

@@ -1,17 +0,0 @@
-version: '3'
-
-services:
-  xandikos:
-    build: docker/xandikos/
-    ports:
-      - '8000:8000'
-
-  radicale:
-    build: docker/radicale/
-    ports:
-      - '8001:8001'
-
-  baikal:
-    build: docker/baikal/
-    ports:
-      - '8002:80'

docs/contributing.rst

@@ -102,8 +102,8 @@ initialized and documented.
 
 For example, to test xandikos, first run the server itself::
 
-    docker-compose build xandikos
+    docker build -t xandikos docker/xandikos
-    docker-compose up -d xandikos
+    docker start -p 8000:8000 xandikos
 
 Then run the tests specifying this ``DAV_SERVER``, run::
 

scripts/tests.template

@@ -3,7 +3,6 @@
 image: archlinux
 packages:
   - docker
-  - docker-compose
   - python-pip
 sources:
   - https://github.com/pimutils/vdirsyncer

tests/storage/servers/baikal/install.sh

@@ -1,4 +1,6 @@
 #!/bin/sh
 
-docker-compose build baikal
+cd $(git rev-parse --show-toplevel)
-docker-compose up -d baikal
+
+docker build -t baikal docker/baikal
+docker run -d -p 8002:80 baikal

tests/storage/servers/radicale/install.sh

@@ -1,4 +1,6 @@
 #!/bin/sh
 
-docker-compose build radicale
+cd $(git rev-parse --show-toplevel)
-docker-compose up -d radicale
+
+docker build -t radicale docker/radicale
+docker run -d -p 8001:8001 radicale

tests/storage/servers/xandikos/install.sh

@@ -1,4 +1,6 @@
 #!/bin/sh
 
-docker-compose build xandikos
+cd $(git rev-parse --show-toplevel)
-docker-compose up -d xandikos
+
+docker build -t xandikos docker/xandikos
+docker run -d -p 8000:8000 xandikos