#core.Start

1 messages · Page 1 of 1 (latest)

umbral gull
#

Hi,
Do you want to use these options to have long-running containers ?

heady bramble
#

I want to use them for sidecars, like if a test run needs a db sidecar, I want to be able to start the db container and then stop it once the tests finish.

uneven arrow
#

@heady bramble They haven't been fully implemented yet: https://github.com/dagger/dagger/issues/3037
https://github.com/dagger/dagger/issues/3173
https://github.com/dagger/dagger/pull/3123

GitHub
Support for Services · Issue #3037 · dagger/dagger

Services: Run asynchronously (can be started and stopped) Aren't cached in their execution Can expose sockets (and similar concepts like TTYs). One classic use case is an e2e test that need...

GitHub
finish the services API · Issue #3173 · dagger/dagger

The services API is incomplete. Mainly: Convert to New Core API Restructure to be multi-process (just like buildkit) Support non-interactive mode (e.g. for launching a db etc, we don't want...

GitHub
services support by aluzzardi · Pull Request #3123 · dagger/dagger

This PR adds support for services, specifically:

Creating services (asynchronous containers)
Service control (listing, retrieving, stopping, ...)
tty streaming over WebSocket with CLI support (clo...

heady bramble
#

cool thanks!