211: fix(modules/service/nixos-init): Use `boot.tmp.useTmpfs` option instead of `boot.tmpOnTmpfs` r=roberth a=MartinNikov
This change fixes the following warning:
```
trace: Obsolete option `boot.tmpOnTmpfs' is used. It was renamed to `boot.tmp.useTmpfs'.
```
This option was renamed in this PR:
https://github.com/NixOS/nixpkgs/pull/204534
Co-authored-by: MartinNikov <99672862+MartinNikov@users.noreply.github.com>
This change fixes the following warning:
```
trace: Obsolete option `boot.tmpOnTmpfs' is used. It was renamed to `boot.tmp.useTmpfs'.
```
This option was renamed in this PR:
https://github.com/NixOS/nixpkgs/pull/204534
209: fix: services.<name>.service.build.context r=roberth a=LoveIsGrief
- [x] Support services.<name>.service.build.context see 638c4b8 for more details
- [x] Add test
Closes#208
Co-authored-by: LoveIsGrief <loveisgrief@tuta.io>
These are simple tests to make sure that the generated docker-compose.json
looks like it should. This means has a build.context and does NOT
have an image defined - the image is built when starting the service.
One could declare it, but it was unceremoniously ignored.
A "localhost/" image was created with pretty much nothing in it
and it couldn't be launched.
The cause was services.<name>.service.image being always set
and subsequently thugs services.<name>.image.nixBuild being truthy.
That would build an image and write the services.<name>.image field
in the docker-compose.json. It leads to the build.context being
ignored and the service failing.
This was solved by only writing services.<name>.service.image when
services.<name>.service.build.context is not set.
services.<name>.image.nixBuild is additionally set to false when
the context is set.
Related to #208
200: Improve service.networks r=roberth a=pedorich-n
This PR adds more options to `service.networks`, according to the [spec](https://docs.docker.com/compose/compose-file/compose-file-v3/#networks) it exposes:
- `aliases`
- `ipv4_address`
- `ipv6_address`
A more complex example using these options is added, by modifying the existing `traefik` example.
I wasn't able to run the tests locally on my non-NixOS machine, but from what I can see, it just tests if the host is available.
That is still true and works, I checked by running `arion up` from the `examples/traefik` folder.
Co-authored-by: Nikita Pedorich <pedorich.n@gmail.com>
It is either flaky or caused by an update in NixOS/Nixpkgs.
Probably not the podman update though, because I've specifically
tested it with that pr at the time.
