sander

@srid, would you be able to test whether it works with `useDaemon: false`? Your self-hosted runner is running inside a nixos-container, correct?

> What's this setting? It disables the daemon+post-build-hook push method. ```yaml - uses: cachix/cachix-action@v14 with: useDaemon: false ``` I've been chipping away at setting up a similar runner in a...

Basic repro: 1. Create `/etc/script.sh` on the server (not in the container): ```sh #!/bin/sh echo "oh hi there" ``` ```console chmod +x /etc/script.sh ``` 2. In a GitHub actions workflow:...

What OS are you using? And what is `SHELL` set to before `nix develop`?

> But I would hope that this behavior should be independent of the OS, since this is one of main reason for using devenv in the first place. Well, you...

Relevant example: https://github.com/cachix/devenv/issues/1104#issuecomment-2068232549

#### Regular flake I can successfully run `devenv up` inside a `direnv` shell, but it fails when run from a shell created with `nix develop --impure`. Not sure what the...

The socket isssue is macos-specific. Our runtime dir is: `DEVENV_RUNTIME=/tmp/devenv-8e7ea8e` The tmp dir in `nix develop --impure` shell is: `TMP=/tmp/nix-shell.uRu0AU` process-compose is looking for the socket in: `/tmp/nix-shell.uRu0AU/devenv-8e7ea8e/pc.sock`

I believe what's happening is that devenv never creates the `/tmp/nix-shell.uRu0AU/devenv-8e7ea8e` directory. Before `nix develop` takes over the shell, the runtime dir is set to `/tmp/devenv-` and created. After `nix...

@domenkozar, see https://github.com/cachix/devenv/issues/1153#issuecomment-2068078326. There's 2 ways to fix this: 1. Re-run `mkdir` in the `procfileScript` to create the new runtime dir. Could be problematic if anything is put into the...