microscaling/imagelayers

Every image weighs 0B

Opened this issue · 15 comments

Hyzual commented

Hi,

I think you probably noticed this but every badge I put on my images reports them weighing 0B.
By the way thanks for making and sharing imagelayers, it's a great help for thinning down docker images !

winsento commented

+1

ckleban commented

Not all images seen to show this. For example, this seems to work fine: https://hub.docker.com/_/registry/

cron410 commented

Is there anything I can do in the meantime in the Dockerfile to get this working correctly?

cron410 commented

So now you are just blocking images that show as 0bytes?
image

tboerger commented

Looks like it's not blocked, but it fails to find the image with tag for a huge amount of images :(

  • 👍1
ssteinerx commented

This product, as far as I can tell, is completely broken. Shame, too. It was very useful when it worked.

  • 😕1
styfle commented

The following images could not be found: mysql:latest

It hasn't been working for a couple months 😕

kost commented

Still does not work...

ttben commented

Maybe this is due to Docker Registry API which is currently in v2?

For example this will works on v2 and not on v1

  1. https://registry.hub.docker.com/v2/repositories/serioja90/rabbitmq/tags/ : Return 200 and content
  2. https://registry.hub.docker.com/v1/repositories/serioja90/rabbitmq/tags/ : Returns 404
  3. https://registry.hub.docker.com/v1/repositories/serioja90/rabbitmq/tags : Returns 200 empty

Notice that the second example has a / at the end whereas the third does not have one.

I think, using your software, that you exclusively handle v1 registry api since it is based on github.com/CenturyLinkLabs/docker-reg-client/registry which has openly said that it does not work anymore...

Maybe this project, wrapped into a webserver, will be a good substitute (OR WILL ONLY WORK FOR V2) !

rossf7 commented

Hi @ttben yes the problem is that the current client only supports V1 of the Registry API. Thanks for suggesting the V2 client from Heroku. I hadn't seen that and it could help with fixing this.

ttben commented

I you aim to wrap both projects (current imagelayers, handling v1, and heroku client which supports v2), please keeps me updated !
I think wrapping them together would make sense.

Hipska commented

Any update on this?

styfle commented

There is an alternative called MicroBadger.
For example: https://microbadger.com/images/node:8.1.2-alpine

  • 👍1
cron410 commented

Microbadger has been working for me for the most part. Disappointing that imagelayers is still completely broken almost 2 years later.