From 121321ba3c64c2a794d4df12a5ad73776816db2f Mon Sep 17 00:00:00 2001 From: Pim Kunis Date: Fri, 3 May 2024 19:54:03 +0200 Subject: [PATCH] Fix link to post --- .../2024-05-03-i-tried-forgejo-actions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/_posts/i-tried-forgejo-actions/2024-05-03-i-tried-forgejo-actions.md b/src/_posts/i-tried-forgejo-actions/2024-05-03-i-tried-forgejo-actions.md index 038c878..d71cf92 100644 --- a/src/_posts/i-tried-forgejo-actions/2024-05-03-i-tried-forgejo-actions.md +++ b/src/_posts/i-tried-forgejo-actions/2024-05-03-i-tried-forgejo-actions.md @@ -39,7 +39,7 @@ This does however require to run the image as a privileged container, and (spoil # Using Forgejo Actions to build Nix derivations -Both the static website and container image for my blog are built using Nix (which I wrote about [here]({% post_url nix-jekyll-derivation/2024-05-03-nix-jekyll-derivation.md %})). +Both the static website and container image for my blog are built using Nix (which I wrote about [here]({% post_url nix-jekyll-derivation/2024-05-03-nix-jekyll-derivation %})). Therefore, it made sense to me to use the [official Docker image](https://hub.docker.com/r/nixos/nix). However, it seems Forgeo Actions has an undocumented dependency on `/bin/sleep` being present inside the container image. It seems sleep is being used to check whether the image is working correctly.