Provide a function that makes it easier to join sets of different systems #16
Comments
|
What do you think of this approach? {
outputs = { nixpkgs, flake-utils, ... }:
flake-utils.lib.eachDefaultSystem (system:
(nixpkgs.lib.optionalAttrs (system == "x86_64-linux") {
image = <drv>;
}) // {
somethingElse = <drv>;
});
}I think it's better because it doesn't expose the |
|
Thats a great idea! |
|
Okay, in that case there isn't much to do. Maybe document the design pattern somewhere, not sure where though. |
|
This helped me, I think it would be nice to have in the README.md |
|
I have a new variation of this that's a little more complex, because I have other derivations that need to refer to the Linux-specific Docker image derivation. Here's what I came up with, but it's pretty atrocious: outputs = { self, nixpkgs, flakeUtils }:
let
systemOutputs = flakeUtils.lib.eachDefaultSystem
(system:
let
pkgs = nixpkgs.legacyPackages.${system};
devPackages = [
pkgs.coreutils-full
pkgs.curl
pkgs.jq
];
in
rec {
packages = pkgs.lib.optionalAttrs (system == "x86_64-linux") {
image = pkgs.dockerTools.buildLayeredImage {
name = "hello-nix";
contents = devPackages;
config = {
Cmd = [ "${pkgs.bashInteractive}/bin/bash" ];
};
};
};
devShell = devShells.base;
devShells = {
base = pkgs.mkShell {
packages = devPackages;
};
};
});
in
# This needs to be separate to allow referring to the linux version of packages.image.
systemOutputs // flakeUtils.lib.eachDefaultSystem (system:
let
# Even on Mac we still build and run a Linux Docker image.
image = systemOutputs.packages.x86_64-linux.image;
pkgs = nixpkgs.legacyPackages.${system};
in
rec {
defaultPackage = image;
apps = {
# packages.image builds a docker image as a tar.gz, so here's a quick wrapper script that
# loads it into your local docker and runs it.
dockerApp = pkgs.writeShellScriptBin "run-docker" ''
echo "Loading docker image from ${image}"
sudo docker load < "${image}"
sudo docker run --rm -it "${image.imageName}:${image.imageTag}"
'';
};
defaultApp = apps.dockerApp;
});As you can see it makes it so that the |
|
Alright, after nearly giving up I did some refactoring to shuffle things around and I still don't love this, but I think it's reasonable-ish. Certainly better than my previous comment. outputs = { self, nixpkgs, flakeUtils }:
let
devPackages = p: [
p.coreutils-full
p.curl
p.jq
p.cowsay
];
linuxPkgs = nixpkgs.legacyPackages.x86_64-linux;
image = linuxPkgs.dockerTools.buildLayeredImage {
name = "hello-nix";
contents = devPackages linuxPkgs;
config = {
Cmd = [ "${linuxPkgs.bashInteractive}/bin/bash" ];
};
};
in
flakeUtils.lib.eachDefaultSystem (system:
let
pkgs = nixpkgs.legacyPackages.${system};
in
rec {
packages = (pkgs.lib.optionalAttrs (system == "x86_64-linux") {
image = image;
}) // {
# Other packages (built on any system) would go here.
};
# Even on Mac we still but the Linux version of a Docker image.
defaultPackage = image;
apps = {
dockerApp = pkgs.writeShellScriptBin "run-docker" ''
echo "Loading docker image from ${image}"
sudo docker load < "${image}"
sudo docker run --rm -it "${image.imageName}:${image.imageTag}"
'';
};
defaultApp = apps.dockerApp;
devShell = devShells.base;
devShells = {
base = pkgs.mkShell {
packages = devPackages pkgs;
};
};
});If anyone has better approaches it would be appreciated! |
|
@chasecaleb I just independently retraced a bunch of what you did, I'm still trying to get a feel for this stuff too. Simplifying some details away: I get this output tree for my actual (a bit more complex) flake EDIT: Fixed a mistake in the code |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a flake that provides a docker image as package in its output.
All but docker image are buildable and should run on the "default systems", so I wanted to move the docker image out of the function into its own attribute set which I then merge them, though due to the way
//works, onepackagesoverwrites the other:will create a flake only provides
somethingElsefor the default systems, if you turn it around to beYou will end up with the
x86_64-linux.imageonly.a
mergeOutputscould take a list of attribute sets thats then gets deepmerged, usage would be roughly:The text was updated successfully, but these errors were encountered: