5. Start LEAF-Writer again and force a pull from the registry for all containers that are not locally build: `sudo docker compose --env-file leafwriter.env -f docker-compose.yml up --build --pull always`. You can add the `-d` flag if you feel brave and want to start everything directly in background. Otherwise it may be a good idea to first check the outputs, then stop the containers with `Ctrl+c`, run `sudo docker compose --env-file leafwriter.env -f docker-compose.yml down` and as the last step, if the output logs where fine and LEAF-Writer was reachable and worked reasonably well, start everything in detached mode with `sudo docker compose --env-file leafwriter.env -f docker-compose.yml up -d`
5. Start LEAF-Writer again and force a pull from the registry for all containers that are not locally build: `sudo docker compose --env-file leafwriter.env -f docker-compose.yml up --build --pull always`. You can add the `-d` flag if you feel brave and want to start everything directly in background. Otherwise it may be a good idea to first check the outputs, then stop the containers with `Ctrl+c`, run `sudo docker compose --env-file leafwriter.env -f docker-compose.yml down` and as the last step, if the output logs where fine and LEAF-Writer was reachable and worked reasonably well, start everything in detached mode with `sudo docker compose --env-file leafwriter.env -f docker-compose.yml up -d`
**Note**:
**Note**: Docker will not automatically remove any old images. Therefore, your hard disk will be cluttered with old images. It is important to regularly clean them up. Since Docker is a very intuitive concept, cleaning unused images and containers is left as an exercise to the reader. And yes, that is sarcasm.
