Skip to content

Unclear bug when using a unix:// store #13152

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

Open
2 tasks done
fzakaria opened this issue May 7, 2025 · 1 comment
Open
2 tasks done

Unclear bug when using a unix:// store #13152

fzakaria opened this issue May 7, 2025 · 1 comment
Labels

Comments

@fzakaria
Copy link
Contributor

fzakaria commented May 7, 2025

Describe the bug

I would like to test chaining stores (what a neat concept!) but I ran into a weird issue as soon as I tried this.

(note: the "unexpected errors happen after I Ctrl-C. The weird issue is the ever increasing PID when trying to do a nix-build against this daemon)
asciicast

Steps To Reproduce

In one terminal run the following

> NIX_DAEMON_SOCKET_PATH=/tmp/nix_socket nix daemon --debug

In another terminal run:

> nix build nixpkgs#hello --store unix:///tmp/nix_socket

Expected behavior

It should build by propagating through this interim daemon which itself forwards to my local daemon (NixOS)

Metadata

nix-env (Nix) 2.28.3

Checklist


Add 👍 to issues you find important.

@fzakaria fzakaria added the bug label May 7, 2025
@fzakaria
Copy link
Contributor Author

fzakaria commented May 7, 2025

I think this has to do with the fact I started the daemon as non-root

When I changed to the following it worked (separate store):

NIX_DAEMON_SOCKET_PATH=/tmp/nix_socket nix daemon --debug --store /tmp/chain
accepted connection from pid 61705, user fmzakari (trusted)
executing Nix database schema migration '20220326-ca-derivations'...
received daemon op 19

Seems like something isn't caught and instead the daemon endlessly tries to build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant