From ead8fea7c7ca1d07023edca8346ec30f49320fba Mon Sep 17 00:00:00 2001 From: Quentin Dufour Date: Sat, 10 Aug 2024 19:25:28 +0200 Subject: [PATCH] explain env thing --- _posts/2024-08-10-fast-ci-build-with-nix.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/_posts/2024-08-10-fast-ci-build-with-nix.md b/_posts/2024-08-10-fast-ci-build-with-nix.md index 010c806..e1f1aa1 100644 --- a/_posts/2024-08-10-fast-ci-build-with-nix.md +++ b/_posts/2024-08-10-fast-ci-build-with-nix.md @@ -105,6 +105,8 @@ volumes: nix: ``` +Note that the volume is named `woodpeck_nix` and not `nix` in the woodpacker agent configuration (`WOODPECKER_BACKEND_DOCKER_VOLUMES` environment declaration). It's because our `docker-compose.yml` is in a `woodpecker` folder and docker compose prefixes the created volumes with the name of the deployment, by default the parent folder name. The prefix is not needed elsewhere, as elsewhere, the resolution is dynamically done by compose. But the `WOODPECKER_BACKEND_DOCKER_VOLUMES` declaration is not part of compose, it will be used later by woodpecker when interacting directly with the Docker API. + Then, in your project `.woodpecker.yml`, you can seemlessly use nix and enjoy efficient and quick caching: ```yml