engine-image-entries

Overview ¶

Command engine-image-entries exports the cache entries an engine image ships for Go module runtimes, on an engine of the image's own build: the builds of the standard library and of what every Go module's generated code imports, as dagger/go builds them, with the module downloads and the tools those builds read, dagger/go's gobuild binary, and what a fresh engine would otherwise fetch to build with them: dagger/go's checkout, the golang image the builds run in and the image gobuild runs in. The engine merges them into its cache at start.

It loads the built-in Go SDK module from -builtin-go-sdk, and dagger/go as that module's dependency go, and fails unless -entrypoint-dagger-go, the dagger/go go-sdk's generated modules depend on, names the same, so that every result is the one their builds look up. It takes what codegen's archives of each Go module in -seed read from the cache (archiveBuilds of its root package, its dependencies alone, without tests), at -go-version with the Go SDK's build flags (distconsts.GoSDKBuildFlags), or for an -entrypoint-seed with dagger/go's own, as go-sdk's entrypoints build; gobuild's binary and the image its calls run in, which its entrypoint declares (Module._prebuild and Module._runtimeImage); and exports them with their blobs into -out.