#Failures pulling docker images from private repository

1 messages · Page 1 of 1 (latest)

covert moon
#

Recently, my builds have started failing because Dagger is unable to pull images from private DockerHub repositories. This started happening with version 0.18.4, after working fine for a long time. The same errors occur after upgrading to 0.18.7.

With all my private images, I'm seeing failures like this:

resolving docker.io/myrepo/my_image:my_tag 0.1s
│ │ ! failed to do request: Head "https://registry-1.docker.io/v2/myrepo/my_image/manifests/my_tag": context canceled
│ │ │ ✔ HTTP GET 0.0s
│ │ │ ✘ remotes.docker.resolver.HTTPRequest 0.0s
│ │ │ ! context canceled
│ │ │ │ ✘ HTTP HEAD 0.0s
│ │ │ │ ! context canceled

It was working fine using the docker login of the host executing the dagger command previously. I have tried adding explicit authorization using with_registry_auth and get the same errors.

Any help understanding this problem would be appreciated.

fiery fractal
#

Do you have dagger cloud enabled? If so, can you share a link to a run where this happened? context canceled makes me wonder if something is going wrong elsewhere and this is just the error that bubbles up most prominently

covert moon
#

Hi Erik, no I don't have dagger cloud enabled. Can you suggest a way to debug whether there is some other problem?

fiery fractal
#

If you can share the full output from the TUI when it happens, that would be a decent replacement for dagger cloud.

Running the command with dagger --progress=plain -vvvv <rest of command> will make it easier to share and also ensure all debug progress is present

covert moon
#

Thanks, will try that...

covert moon
#

To follow-up on this, while the verbose output did not help find the issue, the error message was indeed misleading, as Erik suggested. It turns out we incorrectly configured two services with the same port number, causing a startup failure. I'm curious why Dagger isn't able to bubble up the root error.