cardano-node icon indicating copy to clipboard operation
cardano-node copied to clipboard

Docker Hub does not contain latest release

Open gernotpokorny opened this issue 1 year ago • 7 comments

The current latest release is 8.7.2, which got published 3 days ago, but it got not pushed to Docker Hub. The latest image on Docker Hub got pushed 2 months ago from IOHK. Can you please push an image of the latest release to Docker Hub?

gernotpokorny avatar Dec 11 '23 20:12 gernotpokorny

In fact, the 8.7.2 release does not include the binary assets.

arcenik avatar Dec 12 '23 13:12 arcenik

What you mean, can you please explain in more detail? According to the release notes there were changes to the cli. Thanks.

gernotpokorny avatar Dec 14 '23 00:12 gernotpokorny

On https://github.com/input-output-hk/cardano-node/releases/tag/8.7.2 you have only source code

image

On https://github.com/input-output-hk/cardano-node/releases/tag/8.7.1-pre

image

arcenik avatar Dec 14 '23 10:12 arcenik

And what is the reason for that, why do you not include binary assets?

The last image was published 3 months ago, since then where were many feature releases, bug fixes and even breaking changes. You say there is no reason to publish a new docker image since 3 months? What is the factor for you that determines when you publish a new docker image? I understand if you do not publish an image when you make changes that do not affect the image, but this is not the case here and I would publish it anyway. Why not just upload an image for each increase of the version number? Just keep things simple, I guess you build an image anyway for each new versions in your pipelines?

gernotpokorny avatar Dec 14 '23 17:12 gernotpokorny

Clarification: I am not in charge of any of this. I've just noticed the absence of binary files and added a comment on this issue to avoid duplicate.

arcenik avatar Dec 14 '23 19:12 arcenik

see https://github.com/IntersectMBO/cardano-node/issues/5578

arcenik avatar Dec 21 '23 14:12 arcenik

Maybe there is no binary because there is an error during build when following the instructions that work for previous versions.

rem-wiz avatar Dec 25 '23 03:12 rem-wiz