-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add nom run #110
Comments
The problem is, that once nix finishes fetching or building the program it starts running it. And then piping stdout and stdin through nom is most likely not what you want. Imagine how broken this would be if you do |
I see, I mostly use it with https://github.com/nlewo/nix2container and current output is good enough. |
A not very clean but simple solution would be to translate the This way all output paths are cached and |
Or we go bold and try to mirror the eval which nix run does with nix shell and then execute the process in the shell. I guess if one looks a while hard at the implementation of nix run it won’t be to hard to find a passable solution. |
Is there a reason why
nix run
does not have equivalent in nom?I'm able to use:
nix run --log-format internal-json .#docker.copyToDockerDaemon |& nom --json
and it seems to work.The text was updated successfully, but these errors were encountered: