Changeset View
Changeset View
Standalone View
Standalone View
docker/README.md
Show First 20 Lines • Show All 655 Lines • ▼ Show 20 Lines | (swh)$ docker-compose \ | ||||
run \ | run \ | ||||
swh-journal-backfiller \ | swh-journal-backfiller \ | ||||
snapshot \ | snapshot \ | ||||
--start-object 000000 \ | --start-object 000000 \ | ||||
--end-object 000001 \ | --end-object 000001 \ | ||||
--dry-run | --dry-run | ||||
``` | ``` | ||||
## Using Sentry | ## Using Sentry | ||||
All entrypoints to SWH code (CLI, gunicorn, celery, ...) are, or should be, | All entrypoints to SWH code (CLI, gunicorn, celery, ...) are, or should be, | ||||
intrumented using Sentry. By default this is disabled, but if you run your | intrumented using Sentry. By default this is disabled, but if you run your | ||||
own Sentry instance, you can use it. | own Sentry instance, you can use it. | ||||
To do so, you must get a DSN from your Sentry instance, and set it as the | To do so, you must get a DSN from your Sentry instance, and set it as the | ||||
value of `SWH_SENTRY_DSN` in the file `env/common_python.env`. | 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 | You may also set it per-service in the `environment` section of each services | ||||
in `docker-compose.override.yml`. | 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 | |||||
ardumont: persistent | |||||
`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. |
persistent