technofab/kubenix
1
0
Fork 0
mirror of https://github.com/TECHNOFAB11/kubenix.git synced 2025-12-13 00:20:07 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs: cleanup, fix links, add comments

Browse source
This commit is contained in:
Bryton Hall 2023-06-03 02:38:28 -04:00
parent 8d10d79cfe
commit 95504f4c3b
12 changed files with 65 additions and 82 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/content/examples/image/_index.md
View file

@ -4,8 +4,8 @@ weight: 30
Instead of deploying a 3rd party image, we can build our own.
We rely on the upstream [`dockerTools`](https://github.com/NixOs/nixpkgs/tree/master/pkgs/built-support/docker) package here.
Specifically, we can use the `buildImage` function to define our image:
We rely on the upstream [`dockerTools`](https://nixos.org/manual/nixpkgs/stable/#sec-pkgs-dockerTools) package here.
Specifically, we can use the `buildLayeredImage` function to define our image:
{{< source "image.nix" >}}
@ -60,7 +60,5 @@ Render the generated manifests again and see that it now refers to the newly bui
Of course, to actually deploy, we need to push the image to our registry. The script defined at {{< option "docker.copyScript" >}} does just that.
```sh
$(nix build -f . --json config.docker.copyScript | jq -r '.[].outputs.out')
$(nix build -f . --print-out-paths config.docker.copyScript)
```
<!-- TODO: can we make that `nix run -f . config.docker.copyScript` ? -->