marsh glacier
Hi everyone! I'm new in Dagger. I'm following the steps on this page: https://docs.dagger.io/quickstart/env/
When I use the command "dagger call build-env --source=.", Dagger works correctly. But when I add "terminal --cmd=bash" to the command, I get this error:
Error: response from query: input: container.from.withDirectory.withMountedCache.withWorkdir.withExec.terminal resolve: failed to forward exit code: failed to close terminal: EOF
The full console output can be seen in the image.
coarse nymph
Hi everyone! I'm new in Dagger. I'm following the steps on this page: https://do...
Thanks for the report, I am looking into this now!
glad rivet
Looking at the trace (https://v3.dagger.cloud/DaggerTest/traces/b14c2049127f6e8265ad99253a582321?listen=fd94b6e36d9bb1b7) it looks like bash actually ran correctly inside the container, but something went wrong in your client environment. Possibly related to being on Windows?
coarse nymph
Looking at the trace (https://v3.dagger.cloud/DaggerTest/traces/b14c2049127f6e82...
Sweet, I am actually on windows at the moment too, trying to repro.
coarse nymph
@marsh glacier thanks for the bug report I am able to reproduce this on windows,
I tried this in Powershell, Windows Terminal, CMD.EXE, built-in terminal in VS Code, and even MiniGW that comes with git bash, I get the same error.
It looks like this issue was reported last week (Thanks @marble dragon!)
https://github.com/dagger/dagger/issues/9096
the only place I am able to get the terminal to work is in WSL - do you happen to use WSL at all? That should at least help you keep moving through the quickstart while we look into getting this fixed.
