Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker image not found #132

Open
IlFog opened this issue Oct 29, 2024 · 1 comment
Open

Docker image not found #132

IlFog opened this issue Oct 29, 2024 · 1 comment

Comments

@IlFog
Copy link

IlFog commented Oct 29, 2024

Hi,

I was looking to install your software through docker, so I ran:

$ docker search ModelPolisher
NAME                      DESCRIPTION                                     STARS     OFFICIAL
mephenor/modelpolisher                                                    0
schmirgel/modelpolisher                                                   0
schmirgel/mpserver        Server Implementation for the ModelPolisher …   0

I tried to pull both images, but the command gave this issue:

Using default tag: latest
Error response from daemon: manifest for mephenor/modelpolisher:latest not found: manifest unknown: manifest unknown

Is this correct? Should I use a different method to install ModelPolisher?

Thank you for your help.

IlFog

@Schmoho
Copy link
Collaborator

Schmoho commented Dec 1, 2024

Hello,

The repos do not actually contain a latest tag, see here:
https://hub.docker.com/r/schmirgel/modelpolisher/tags
https://hub.docker.com/r/mephenor/modelpolisher/tags

Please note that the mephenor repo is no longer maintained.

For context: the latest tag does not by default represent the "latest" version of an image, see this blog post for explanation:
https://medium.com/@mccode/the-misunderstood-docker-tag-latest-af3babfd6375
Furthermore, keep in mind that when using the latest tag of an image, you open yourself up to possible breakage when newer/other versions of an image are released under this tag that may not be guaranteed to be compatible with your usage scenario.

That is why I have opted to not push a latest tag to begin with. If that causes problems for users we might reconsider this policy (@draeger Any opinions on this?), but for now I would recommend you to explicitly use the :2.1 tag.

I added a "documentation" tag on this issue because this should probably documented explicitly in our README.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants