#Timeout for engine pulls in ci

1 messages · Page 1 of 1 (latest)

grand cedar
#

I'm using dagger's github action but every few runs i get a timeout

7 : ┆ exec docker info DONE [0.4s]
2 : ┆ starting engine
3 : ┆ ┆ create container
6 : ┆ ┆ ┆ exec docker pull registry.dagger.io/engine:v0.19.6 ERROR [15.0s]
6 : ┆ ┆ ┆ ! failed to run command [docker pull registry.dagger.io/engine:v0.19.6]: exit status 1
3 : ┆ ┆ create container ERROR [15.1s]
3 : ┆ ┆ ! failed to pull image: failed to run command [docker pull registry.dagger.io/engine:v0.19.6]: exit status 1
2 : ┆ starting engine ERROR [15.1s]
2 : ┆ ! failed to pull image: failed to run command [docker pull registry.dagger.io/engine:v0.19.6]: exit status 1
1 : connect ERROR [15.4s]
1 : ! start engine: failed to pull image: failed to run command [docker pull registry.dagger.io/engine:v0.19.6]: exit status 1
2 : ┆ starting engine
3 : ┆ ┆ create container
6 : ┆ ┆ ┆ exec docker pull registry.dagger.io/engine:v0.19.6 ERROR [15.0s]
6 : ┆ ┆ ┆ ! failed to run command [docker pull registry.dagger.io/engine:v0.19.6]: exit status 1
6 : ┆ ┆ ┆ [15.0s] | Error response from daemon: Get "https://registry.dagger.io/v2/": net/http: request canceled (Client.Timeout exceeded while awaiting headers)

is that common?

dense shard
#

Hi @grand cedar! I'm sorry you are seeing this issue. This is a transient error that should go away with a retry. We are working to improve our registry infra and make it more reliable! 💪

grand cedar
#

@dense shard yes I am retrying but this is happening on every 3rd pipeline, and we have multiple pipelines with dagger with fail, kinda tidious to keep re-trying. Is it possible to add a registry as a fallback or even define my own registery which I'll upload the dagger engine to and then pull it ?

dense shard
#

Right now there is no way of configuring a custom image for the engine. We have just now scaled up our registry on a few regions. Can you let me know if it improves over the next few hours?

grand cedar
#

Thanks, will update
Maybe it's possible to cache the layers of the dagger engine to github actions (via the dagger action) to avoid pulling from the registry everytime?

sharp bobcat