[SOLVED] Interactive terminal (shell) for debugging (not dagger module) | Dagger | Page 1

earnest lynx Jan 24, 2025, 1:48 PM

#

Hi, I have a Golang stand-alone project which is using Dagger under the hood. And I would like to use the interactive terminal for occasional debugging in case of error.

However it seems that interactive terminal is only supported in dagger modules. Unfortunately my golang project is not a dagger module. Is there a way to still use this?

For a while I was using a SSH workaround - in case of error, convert the container into service and open SSH server, to which I can connect and I can debug whatever is wrong.

vital tapir Jan 24, 2025, 1:52 PM

#

Should work with dagger run. Are you using it?

earnest lynx Jan 24, 2025, 1:52 PM

#

No, because it is not dagger module 😦

vital tapir Jan 24, 2025, 1:55 PM

#

dagger run doesn't work with modules. It's for custom scripts. Like dagger run go run script.go.

earnest lynx Jan 24, 2025, 1:55 PM

#

oh

vital tapir Jan 24, 2025, 1:56 PM

#

See Dagger SDKs > Custom applications (docs).

earnest lynx Jan 24, 2025, 2:05 PM

#

OK, I see. This seems like exactly what I was looking for. Thanks!

#

Is there a way to get around the dagger run?
It is rather cumbersome to call dagger run --interactive /usr/bin/my-project --arg1 --arg2 . I would be great to somehow hide the dagger run --interactive into the project itself.

solar basin Jan 24, 2025, 2:15 PM

#

earnest lynx Is there a way to get around the `dagger run`? It is rather cumbersome to call `...

no it's not possible since it's the dagger command the one that makes possible for the interactive terminal to work

earnest lynx Jan 24, 2025, 2:15 PM

#

I think that os/exec and child-process would be kinda cursed.

#

But should work.

#

Might be too cursed ...

#

Anyway, thank you a lot for these tips! This is great! I can now drop my SSH workaround that I made in the ancient times before v0.12 came around.

#[SOLVED] Interactive terminal (shell) for debugging (not dagger module)