#14117·dagger

`dagger sdk install go` installs incompatible SDK on beta.11

Author: nineslCreated Sep 11, 2026Updated Sep 11, 2026

What is the issue?

I’m following the Go SDK docs, but dagger sdk install go warns that the SDK has no initModule or initClient. Running dagger module init go hello-world then fails with unknown command "go".

I’m working around this by pinning the SDK to an older commit:

toml
[modules.go]
source = "github.com/dagger/go-sdk@9fef632f5e9c4e6d54c97e128752c991d3cda306"

[modules.go.as-sdk]

What my agent thinks is causing the issue

The installed SDK resolves to 043e8c089210667fa38c9d64238075d884cdd66f, which replaced the initialization hooks with generateScope. Beta.11 still expects the old hooks, which the pinned revision retains.

Dagger version

v1.0.0-beta.11 (a4e1e4ff), linux/amd64
runner-host: image://registry.dagger.io/engine:v1.0.0-beta.11

Steps to reproduce

bash
dagger sdk install go
dagger module init go hello-world

Log output

⚠ "go" was installed as an SDK, but it can neither create modules nor
  initialize clients (no initModule or initClient).

Error: unknown command "go" for "dagger module init"