drone-plugins/drone-docker

Unable to reach Docker Daemon after latest release of plugin/docker

Closed this issue · 14 comments

After recent update on plugins/docker we have an issue connecting to container of plugin/docker:

15
By [plugins](https://hub.docker.com/u/plugins)

•
Updated 38 minutes ago


+ /usr/bin/dockerd --data-root /var/lib/docker --host=unix:///var/run/docker.sock
--
5 | Unable to reach Docker Daemon after 15 attempts.
6 | Detected registry credentials file


Hi, same here .. since latest update i get:

latest: Pulling from plugins/docker
Digest: sha256:31531093cbe7bee6c73ab746b531540601a4751b94783c05de45e7c90f3d010e
Status: Downloaded newer image for plugins/docker:latest
+ /usr/bin/dockerd --data-root /var/lib/docker --host=unix:///var/run/docker.sock -s overlay
Unable to reach Docker Daemon after 15 attempts.
Detected registry credentials

Thanks :)

As a temporary solution you can rollback to tag 20.17.4 for Drone plugins plugins/docker, plugins/ecr, plugins/gcr, etc

As a temporary solution you can rollback to tag 20.17.4 for Drone plugins plugins/docker, plugins/ecr, plugins/gcr, etc

yes, that works as workarounds..

I have a lot pipelines. I cannot edit them all and then roll them back after the fix. Please resolve this issue ASAP and inform us when you push a stable version. Thanks! :)

Ping @Ompragash as the creator of the most recent tag.

I think the community would also appreciate if Harness could elaborate on what is building and updating the latest image when there hasn't been any changes in the source code since the last tag.

image image

Dude @Ompragash rollback the changes haha

Having the same issue here, is there a stable tag of plugins/docker we can use in the meantime?

Edit: just saw @smartfin's comment above

I`m having the same issue.

Same issue here

As a temporary solution you can rollback to tag 20.17.4 for Drone plugins plugins/docker, plugins/ecr, plugins/gcr, etc

This works like a charm

@tonglil we have a separate plugins/buildx image that the team is working on, but it was accidentally published to plugins/docker which is the root cause of the failure and also explains why the image was updated despite no code change. We are re-running a pipeline to republish and push plugins/docker to restore the :latest tag with the correct version. The team is updating plugins/buildx to ensure it publishes to the correct dockerhub repository. This should be fixed in ~12 minutes. The team will follow up with more details and can answer any questions. Apologies for the disruption!

Image updated. Please let us know if you have any further issues. @jamie-harness and team will monitor this thread. thanks everyone for your patience.

Verified the plugins/docker:latest plugin/docker (without tag) plugin/docker:20.17.4 all back to correct behavior. If you pulled some of the tags above during this incident you can set the pull policy to aways and run it once (shouldn't be needed for the latest and empty tag). Closing this issue

Image updated. Please let us know if you have any further issues. @jamie-harness and team will monitor this thread. thanks everyone for your patience.

thank you for quick response and fix!