#i have kind of a dumb general docker/go
1 messages · Page 1 of 1 (latest)
as of go 1.22 builds are all reproducible so i guess that's less of a concern now. mostly i am wondering about which way allows more cache usage
You can't go wrong always doing everything in a container. Especially in the context of Dagger, it means your DAG coverage is better - as in , you can see more steps of your pipeline in the Dagger API
It terms of performances, cache usage etc they are equivalent (at least in the case of go)
especially since Go has great cross-compile tooling, so even targeting other platforms works fine from a container