Refrencing files with ./path/to/foo - am I holding it wrong?

This one got me off guard. Been on nixos for several years now, and I always relied on files referenced by ./path/to/foo.env being available on the target machine. tl;dr - I believe there’s a few potential non-obvious things going on in here: files referenced with ./path/to/foo.env not being copied to remote nixos VMs opaquely accessing host’s /nix/store oci-containers’s environmentFiles too lazily evaluated (or not at all) The other day I was setting up managed containers via oci-containe...