Services are lost in interactive shell

[gritty flicker]

Is it possible to keep services alive when using interactive mode? Would be very helpful for debugging.

This example uses a service and throws an error. The debug shell works, but the service is gone.

// interactive shell looses the service dependency currently (0.15.1)
func (m *Treasury) ExperimentWithService(
    ctx context.Context,
) (string, error) {

    service := dag.Container().
        From("python").
        WithWorkdir("/srv").
        WithNewFile("index.html", "Hello, world!").
        WithExposedPort(8080).
        AsService(dagger.ContainerAsServiceOpts{Args: []string{"python", "-m", "http.server", "8080"}})

    out, err := dag.Container().
        From("alpine").
        WithServiceBinding("www", service).
        // use service
        WithExec([]string{"wget", "-O-", "http://www:8080"}).
        // cause error
        WithExec([]string{"false"}).
        Stdout(ctx)
    return out, err

}

I run with dagger -i -v call experiment-with-service

But then inside the debug shell, I the www is gone.

/ # wget http://www:8080
wget: bad address 'www:8080'
/ # cat /etc/hosts 
127.0.0.1       localhost buildkitsandbox
::1     localhost ip6-localhost ip6-loopback
/ # 

[knotty flower]

This would be an amazing issue, if you could open one @gritty flicker 🙏

[gritty flicker]

https://github.com/dagger/dagger/issues/9206

[void oak]

This should work if you add the .Terminal call instead of the -i flag. Having said that, if it's straightforward to implement with -i, I agree it'd be a nice to have

[knotty flower]

I felt the need/desire for this the other day as well while debugging.