Jonas Chevalier

nix defaults to load `/etc/nix/machines` unless the `builders` option is set in `/etc/nix/nix.conf`. When using nix-darwin, it sets `builders =` in the nix.conf by default, which explains the issue.

This decision should be up to @mjlbach as he is the original maintainer. Let's wait a bit to see what he thinks about this idea. It's good that we have...

That would be nice. I am not in a position to do it myself at the moment. Meanwhile, it looks like somebody else went ahead and published that plugin: https://registry.terraform.io/providers/ZenSecurity/secret/latest

@offlinehacker sorry this went out of my radar. Would you like me to merge this PR?

Yeah, that makes sense. I also think that it will be less pain as tooling in vscode tends to assume a debian-like environment.

``` $ drun nixpkgs/nix:nixos-unstable sh -c "cat /etc/*release | grep ^ID" sh: grep: command not found cat: '/etc/*release': No such file or directory ``` The nix image is fairly minimal...

It's possible that GitHub Actions sets a custom entry point for the container. That would explain the error. To test that I would create an image with tons of wrappers...

I am a bit torn. It allows running programs that didn't go through patchelf, which is both a bad and good thing. Depending if the binary was packaged by Nix...

@Mic92 what do you think if we add a GitHub Actions agent on the aarch64 box that we have now? I'm not opposed to the idea, it's just a matter...

An image dedicated to build and push docker images sounds good! Maybe there are other tools that would fit in there. Take a look at `images/cachix`, it should give you...