#Dagger engine delays to publish images to OCI registry

1 messages · Page 1 of 1 (latest)

odd spire
#

I am encountering an issue I didn't have when using v0.9 of the engine which started the process immediately i.e. the delay of publishing to a specified registry.

I have used the Rust sdk because that is what I used with v0.9, and now v0.18.3 , of the dagger engine and benchmarked it with Go's sdk v0.18.3. For the rust one it didn't manage to publish (i.e go past line 50 of the logs) but for Go it delayed and then managed to publish after some few minutes. Seems like a network issue but I dont know its because the engine is running on WSL2 (other than the old previous one on Linux)

Any input will be appreciated...

#

The logs are as follows

29  : Container.publish(address: "ttl.sh/locci-build-1745266469674315500:1h"): String!
30  : │ remotes.docker.resolver.HTTPRequest
31  : │ HTTP HEAD
31  : │ HTTP HEAD ERROR [1.4s]
30  : │ remotes.docker.resolver.HTTPRequest ERROR [1.4s]
32  : │ remotes.docker.resolver.HTTPRequest
33  : │ HTTP HEAD
33  : │ HTTP HEAD ERROR [1.5s]
32  : │ remotes.docker.resolver.HTTPRequest ERROR [1.5s]
34  : │ remotes.docker.resolver.HTTPRequest
35  : │ HTTP HEAD
35  : │ HTTP HEAD ERROR [1.5s]
34  : │ remotes.docker.resolver.HTTPRequest ERROR [1.5s]
36  : │ remotes.docker.resolver.HTTPRequest
37  : │ HTTP HEAD
37  : │ HTTP HEAD ERROR [1.5s]
36  : │ remotes.docker.resolver.HTTPRequest ERROR [1.5s]
38  : │ remotes.docker.resolver.HTTPRequest
39  : │ HTTP HEAD
39  : │ HTTP HEAD ERROR [1.5s]
38  : │ remotes.docker.resolver.HTTPRequest ERROR [1.5s]
40  : │ remotes.docker.resolver.HTTPRequest
41  : │ HTTP HEAD
41  : │ HTTP HEAD ERROR [0.5s]
40  : │ remotes.docker.resolver.HTTPRequest ERROR [0.5s]
42  : │ remotes.docker.resolver.HTTPRequest
43  : │ HTTP HEAD
43  : │ HTTP HEAD ERROR [0.5s]
42  : │ remotes.docker.resolver.HTTPRequest ERROR [0.5s]
44  : │ remotes.docker.resolver.HTTPRequest
45  : │ HTTP HEAD
45  : │ HTTP HEAD ERROR [0.4s]
44  : │ remotes.docker.resolver.HTTPRequest ERROR [0.4s]
46  : │ remotes.docker.resolver.HTTPRequest
47  : │ HTTP HEAD
47  : │ HTTP HEAD ERROR [0.4s]
46  : │ remotes.docker.resolver.HTTPRequest ERROR [0.4s]
48  : │ remotes.docker.resolver.HTTPRequest
49  : │ HTTP HEAD
49  : │ HTTP HEAD ERROR [0.4s]
48  : │ remotes.docker.resolver.HTTPRequest ERROR [0.4s]
50  : │ remotes.docker.resolver.HTTPRequest
51  : │ HTTP HEAD
51  : │ HTTP HEAD ERROR [0.4s]
50  : │ remotes.docker.resolver.HTTPRequest ERROR [0.4s]
tired harbor
# odd spire The logs are as follows ``` 29 : Container.publish(address: "ttl.sh/locci-buil...

👋 just tried pushing our quickstart (https://docs.dagger.io/quickstart/ci) demo to ttl.sh and didn't notice any particular latency issues. Those HTTP HEAD ERROR spans are coming from buildkit which seems to be incorrectly labeling those as errors 🙏

Build a CI Pipeline | Dagger

CI pipelines often start simple, but eventually transform into a labyrinth of artisanal shell scripts and/or unmanageable YAML code. Dagger lets you replace those artisanal scripts and YAML with a modern API and cross-language scripting engine.

odd spire
#

Thanks @tired harbor
Have you tried with the Rust SDK?....
I know its experimental but I would really like to know the output you get...

tired harbor
#

I'll try a simple pipeline in a bit 🙏

odd spire
#

Okay thanks
I will await your feedback

tired harbor
#

it mostly takes time to upload the app layers because they're a bit heavy weight.. but I don't perceive any particular slowness in the Rust SDK