LoveIsGrief 638c4b8e55 fix: services.<name>.service.build.context ... 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		2023-08-20 15:20:34 +02:00
..
default.nix	fix: services.<name>.service.build.context	2023-08-20 15:20:34 +02:00