#Pulling dagger engine image timeouts

1 messages Β· Page 1 of 1 (latest)

molten hatch
#

It looks like the Dagger engine image is timing out during pulls today, this is causing failures and barely stringing some pipelines along πŸ™‚

Pipeline 1:

3   : ┆ ┆ create container
6   : ┆ ┆ ┆ exec docker pull registry.dagger.io/engine:v0.19.11
6   : ┆ ┆ ┆ [15.0s] | Error response from daemon: Get "https://registry.dagger.io/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
6   : ┆ ┆ ┆ exec docker pull registry.dagger.io/engine:v0.19.11 ERROR [15.0s]
6   : ┆ ┆ ┆ ! failed to run command [docker pull registry.dagger.io/engine:v0.19.11]: exit status 1
3   : ┆ ┆ create container ERROR [15.0s]

Pipeline 2:

6   : ┆ ┆ ┆ [3m41s] | 71977856852f: Verifying Checksum
6   : ┆ ┆ ┆ [3m41s] | 71977856852f: Download complete
6   : ┆ ┆ ┆ [3m46s] | 805a2ef245c4: Retrying in 10 seconds
6   : ┆ ┆ ┆ [3m47s] | 805a2ef245c4: Retrying in 9 seconds
6   : ┆ ┆ ┆ [3m48s] | 805a2ef245c4: Retrying in 8 seconds
...
3   : ┆ ┆ create container
6   : ┆ ┆ ┆ exec docker pull registry.dagger.io/engine:v0.19.11 ERROR [9m60s]
6   : ┆ ┆ ┆ ! failed to run command [docker pull registry.dagger.io/engine:v0.19.11]: signal: killed
3   : ┆ ┆ create container ERROR [10m0s]
3   : ┆ ┆ ! failed to pull image: failed to run command [docker pull registry.dagger.io/engine:v0.19.11]: signal: killed
viral pumice
viral pumice
#

@molten hatch should be better now. LMK how it looks

molten hatch
#

The engine image appears to be pulling without issue now. Thanks, @viral pumice!