#Hello, how can i export the engine dev
1 messages ยท Page 1 of 1 (latest)
arm does work locally, just emulation segfaults: please choose naother arch than your native one ๐
strange.. seems to work for me the other way around ๐ค
dagger call dev-export --platform linux/arm64
โ connect 0.2s
โ initialize 4.1s
โ prepare 0.0s
โ daggerDev: DaggerDev! 25.9s
โ DaggerDev.devExport(platform: "linux/arm64"): Directory! 4m45.1s
โ Directory.digest: String! 0.5s
โ Directory.entries: [String!]! 0.3s
Full trace at https://dagger.cloud/marcos-test/traces/873559240a3be64afeca7fd9f9b0092e
_type: Directory
digest: sha256:ac0dae778f75e564563b4757d384aa00444220cc7046b70cd4e429da9bcdca65
entries:
- dagger
- engine.tar
linux/amd64 is what I need. To test in Windows
The qemu emulator is just kind of buggy unfortunately, always has been. It should work on a retry @urban stirrup.
However, I think it's having extra trouble with that go build std step. We could refactor it to do cross compilation instead which should be more reliable +faster than emulation
Hey @thorn flax! The actual reason @urban stirrup even has to make an engine image for me is because I can't make one myself. On my corporate network, even with CA certs installed in my custom image, I can't get the dagger module to work. I keep getting TLS cert errors. I don't think the CA certs are propagating to nested containers properly. I've tested that use case, it does work in most cases but the engine build is doing something that's breaking it.
Hey I unlocked it
Do you have the specific error and step where you are hitting it? Sorry if it was posted somewhere else and I missed it.
Can't promise I can look into it immediately but can at least make a note for it. Or if it's painfully obvious may be able to fix quickly
Let me re-try and get you a better pinpoint
Finally got some time to fiddle with this. This is the command I ran
dagger -m github.com/dagger/dagger@v0.13.5 call engine container --help
It's trying to do codegen for all the required modules and looks like when the CA certs are needed they are not available to them
โ Container.withExec(args: ["codegen", "--output", "/src", "--module-context-path", "/src/modules/alpine", "--module-name", "alpine", "--introspection-json-path", "/schema.json"], experimentalPrivilegedNesting: true): Container! 11.1s
I see many other ones like this. The proxies seem to be fine as it pulls the deps that doesn't do the TLS check.
This is one of the packages that has the issue
github.com/klauspost/compress/zstd: github.com/klauspost/compress@v1.17.9: Get "https://storage.googleapis.com/proxy-golang-org-prod/38aca31a75a6dc59-github.com:klauspost:compress-v1.17.9.zip?Expires=1730562223&GoogleAccessId=gcs-urlsigner-prod%40golang-modproxy.iam.gserviceaccount.com&Signature=hH0zT0CIjyZdWiY56aTIUQgg08KcRT0COgPpIqT8dEkjMyGRnlQzYs%2FO8oNub9%2F2kCWtL7ztLqHlgVnS4IAYg%2Flv%2B5ESyb7G2V0%2Ff%2Fe%2FPJ1j955OJV6qZ9W2JhTzCcdykDpSRRoxn1PFSA7yLNRy%2BQFbD9gq%2B8ZFqeyQ4Q3Cwf9N4lNDhUp85U%2BbhO7L8jl%2FZWMdyO9ZId%2FRyIpTjz6AvzlIK2Z4xY6bMr7XTzRJJu5xtDEeEu0A9RLNjOTTHE0ur8NVZhUPLlrCm5LTfDFT9UMKMY180yjU7N3gqnYA4G32Pk%2Bsd6JFb2C6lJoDVYkOaOodZEf26cQpl1QP4kHy7A%3D%3D": tls: failed to verify certificate: x509: certificate signed by unknown authority
So, I took this one example (github.com/klauspost/compress/zstd) and added an import to a test dagger module. I am still getting the tls error. So it has nothing to do with nesting. I know for a fact that the CA cert is there. Is there some special config for Go that's missing?
FWIW, my local machine is able to pull the dependency with go get and then go mod tidy
Here's my dagger module. Took the example out of the compress module's gh repo.
package main
import (
"io"
"github.com/klauspost/compress/zstd"
)
type Daggertest struct{}
// Compress input to output.
func (d *Daggertest) Compress(in io.Reader, out io.Writer) error {
enc, err := zstd.NewWriter(out)
if err != nil {
return err
}
_, err = io.Copy(enc, in)
if err != nil {
enc.Close()
return err
}
return enc.Close()
}
@thorn flax have you had a chance to look at this? I'm still seeing this on my local.
Hey Nipuna, I think Erik is onto something else atm ; i'd be happy to take a look next week / sync with you to get me to full repro, from scratch
Sounds good @urban stirrup , I think @hushed bone also figured out something related to this.
Just unsure about the status of this cc. @hushed bone (TLS part), as with all the config related work