Hopefully it's not too late to ask this question, but dagger doesn't expect .env to a generic shell-sourceable file.
This would make it unambiguous.
Not the most important issue ever, but I though I'd bring it up.
#Should `.env` be `.daggerenv`?
rain bramble
covert belfry
I do believe it's all changing soon with the introduction of modules v2: https://dagger.io/changelog#modules-v2
You'll soon preset env values in your .dagger/config.toml files
rain bramble
that still leaves the possibility of an unrelated .env file getting in the way though.
Not something that happened to me, but maybe using a more deliberate name is safer.
covert belfry
I don't think it does, my interpretation of Modules V2 is that they won't read .env at all