diff --git a/docker/README.md b/docker/README.md
--- a/docker/README.md
+++ b/docker/README.md
@@ -661,6 +661,7 @@
              --dry-run
 ```
 
+
 ## Using Sentry
 
 All entrypoints to SWH code (CLI, gunicorn, celery, ...) are, or should be,
@@ -671,3 +672,26 @@
 value of `SWH_SENTRY_DSN` in the file `env/common_python.env`.
 You may also set it per-service in the `environment` section of each services
 in `docker-compose.override.yml`.
+
+
+## Caveats
+
+Running a lister task can lead to a lot of loading tasks, which can fill your
+hard drive pretty fast. Make sure to monitor your available storage space
+regularly when playing with this stack.
+
+Also, a few containers (`swh-storage`, `swh-xxx-db`) use a volume for storing
+the blobs or the database files. With the default configuration provided in the
+`docker-compose.yml` file, these volumes are not persistant. So removing the
+containers will delete the volumes!
+
+Also note that for the `swh-objstorage`, since the volume can be pretty big,
+the remove operation can be quite long (several minutes is not uncommon), which
+may mess a bit with the `docker-compose` command.
+
+If you have an error message like:
+
+  Error response from daemon: removal of container 928de3110381 is already in progress
+
+it means that you need to wait for this process to finish before being able to
+(re)start your docker stack again.
diff --git a/docker/tests/test_01_loader_git.sh b/docker/tests/test_01_loader_git.sh
--- a/docker/tests/test_01_loader_git.sh
+++ b/docker/tests/test_01_loader_git.sh
@@ -6,7 +6,7 @@
 
 status_message "Scheduling the loading of the git repository located at ${TEST_GIT_REPO_URL}"
 
-docker-compose $DOCO_OPTIONS exec -T swh-scheduler swh scheduler task add load-git repo_url=$TEST_GIT_REPO_URL
+docker-compose $DOCO_OPTIONS exec -T swh-scheduler swh scheduler task add load-git url=$TEST_GIT_REPO_URL
 
 status_message "Waiting for the git loading task to complete"