apple container | Dagger | Page 1

vernal pier Nov 21, 2025, 9:47 AM

#

dagger can not detect apple container ...

tiny flicker Nov 21, 2025, 9:54 AM

#

There's an order in which dagger will try to detect the right container runtime.
If I read it correctly you have at the same time orbstack and apple container.
To say to dagger to try first with apple container, you have to explicitly say it. For instance, on my machine with both apple container and docker desktop:

$ container system start
Verifying apiserver is running...

$ container ls
ID  IMAGE  OS  ARCH  STATE  ADDR  CPUS  MEMORY

$ _EXPERIMENTAL_DAGGER_RUNNER_HOST=image+apple://registry.dagger.io/engine:v0.19.7 dagger core version
✔ connect 20.3s
✔ loading type definitions 0.3s
✔ parsing command line arguments 0.0s

✔ version: String! 0.0s

v0.19.7

Full trace at https://dagger.cloud/dagger/traces/2b5ee94ef31f30f2c39425ce4aa65576

$ container ls
ID                     IMAGE                              OS     ARCH   STATE    ADDR          CPUS  MEMORY
dagger-engine-v0.19.7  registry.dagger.io/engine:v0.19.7  linux  arm64  running  192.168.64.2  4     8192 MB

The key here is the _EXPERIMENTAL_DAGGER_RUNNER_HOST=image+apple://registry.dagger.io/engine:v0.19.7 with image+apple

vernal pier Nov 24, 2025, 4:44 AM

#

yes, but my orbstack not launched, and , why it can't keep try apple cotainer when orbstack docker daemon connection failed

golden vector Nov 24, 2025, 1:29 PM

#

vernal pier yes, but my orbstack not launched, and , why it can't keep try apple cotainer wh...

hi patrick! as Yves mentioned, Dagger currently picks one OCI provider based on maturity and popularity. It currently doesn't automatically fallback to others.

If you want to use different providers for different dagger calls, you need to use the _EXPERIMENTAL_DAGGER_RUNNER_HOST env variable Yves pointed above

#apple container