btcd icon indicating copy to clipboard operation
btcd copied to clipboard

Published 20 hours ago • verified publisher icon btcsuite

DockerHub image non existant

Open jsfour opened this issue 2 years ago • 8 comments

When I try to pull the latest image from dockerhub it fails:

$ docker pull btcsuite/btcd:latest
Error response from daemon: pull access denied for btcsuite/btcd, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

The btcsuite user does nott seem to exist on dockerhub:

Screen Shot 2022-03-22 at 4 14 40 PM

jsfour avatar Mar 22 '22 23:03 jsfour

Having the same issue. Is there a change in image name?

rasodu avatar May 18 '22 08:05 rasodu

@vpereira01 , Can you help? Documentation may be outdated.

rasodu avatar May 18 '22 09:05 rasodu

Yes, the docs are outdated. You can build your own docker image with the Dockerfile in the repository.

There hasn't been an official docker image from sometime now but I don't know when/how it stopped being built. I have made a PR to build docker images for GitHub registry, instead of DockerHub, but the workflow has not been triggered yet.

The repository collaborators could run manually from the latest release tag but I don't have access.

vpereira01 avatar May 18 '22 10:05 vpereira01

@vpereira01 I don't recall what happened with the original docker builds.

Anyway, I can manually trigger the workflow if that would be helpful. But does it make sense to do it from a non-tagged point in the repo? Or should it wait for a tag?

jcvernaleo avatar May 18 '22 12:05 jcvernaleo

I think it's makes more sense to run it for a previous release tag.

Something like this (image from other repo) image

vpereira01 avatar May 18 '22 13:05 vpereira01

I actually tried that and it doesn't seem to work since the most recent tag pre-dates the workflow: Screenshot 2022-05-18 at 10-04-01 Actions · btcsuite_btcd

Hard to tell in the screenshot, but Run Workflow is not clickable there.

jcvernaleo avatar May 18 '22 14:05 jcvernaleo

Yeah :\ Forgot about that.

Humm, to support building older versions requires extra work which I'm not sure it worth it. So I would advise to wait for the next tag.

Either way, a way to do it would be create a new branch from the previous tag. Cherry-Pick the new workflow to build the image and push it to the GitHub. Then from GitHub it should be possible to run the workflow from that branch. Still it will mess up a bit the meta-data of the Docker image given it's not being built from the tag but from a branch.

vpereira01 avatar May 18 '22 14:05 vpereira01

Sounds to me waiting for next tag is the best solution here (or building locally if it is something you need).

I'd really like to do a new tag/release sooner rather than later.

jcvernaleo avatar May 18 '22 14:05 jcvernaleo