sincecutoff.com
/v1/json /v1/md llms.txt
← all changes

dagger up starts module-defined services on the host

Introduced 2026-04-09 · score 0.92

HOW TO USE IT

When a Dagger module defines a service function marked with `@up` (or the SDK equivalent), run `dagger up` to start its services and expose their ports on the host. Configure `portMappings` when a toolchain service needs a different host port.

dagger up
dagger up -l
{"toolchains":[{"name":"<toolchain>","portMappings":{"<service>":["<host-port>:<service-port>"]}}]}

WHY THIS HELPS

Start a module-defined service on the host while developing a Dagger module.

REQUIREMENTS AND LIMITATIONS

  • Version: v0.20.4
  • Availability: experimental
  • @up / `+up` (required): Mark a function returning `Service` for `dagger up`; SDK syntax varies.
  • `portMappings`: Toolchain config object mapping service names to port mapping strings in `hostPort:servicePort` form. Configure when remapping is needed.
  • `services()`: Workspace API that aggregates services across workspace modules, with include/exclude filtering.
  • Prerequisite: Expose service functions returning `dagger.Service`; annotate them with `+up` or the SDK-equivalent annotation for discovery.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card