Anyone has ever met this issue | Dagger | Page 1

dire oxide Sep 13, 2023, 3:53 PM

#

👋 Searching got me here. How did you fix this? It's just showed up for me.

analog harness Sep 13, 2023, 3:58 PM

#

dire oxide 👋 Searching got me here. How did you fix this? It's just showed up for me.

You need to cleanup your actual engine -> docker prune shall do

#

Then make sure your Dagger CLI / SDK is up to date

#

Update it if not, that should fix the issue 🙂

dire oxide Sep 13, 2023, 4:04 PM

#

A docker prune doesn't work. I'll bump dagger to 0.8.4 then

analog harness Sep 13, 2023, 4:05 PM

#

Make sure clean your images, volumes, network and containers

#

You should not use your old dagger engine image to power up the engine, it shall pull the new one

dire oxide Sep 13, 2023, 4:14 PM

#

Bumping the version did the trick, thanks. Though I now have this issue. I'll try a few things out.

message: 'failed to do request: Head "https://registry-1.docker.io/v2/library/node/manifests/16-slim": dial tcp: lookup registry-1.docker.io on 10.87.0.1:53: read udp 10.87.0.1:58778->10.87.0.1:53: i/o timeout',

#

Last time I got this error a removal of the container was enough but this time it won't go away. Any ideas?

#Anyone has ever met this issue