jlesage/crashplan-pro:latest not found....

[dav1n]

Today, doing a simple docker pull is failing for me:

# docker pull jlesage/crashplan-pro
Using default tag: latest
Error response from daemon: manifest for jlesage/crashplan-pro:latest not found

[jlesage]

Are you using a recent version of Docker ?

[dav1n]

It's the same version on my QNAP that I've been using forever (and I will admit that I have not done a firmware update on the QNAP for quite a long time). So it's likely fairly old, but it has worked for your crashplan-pro up until this latest release, and it still works for other docker pulls.

# docker --version
Docker version 17.09.1-ce, build 0bbe3ac

[dav1n]

I just tested in two ways:

• tried to pull some of your other docker images - and all failed with the same error
• tried to pull some other random docker images I found on dockerhub - and all succeeded.

So something weird is going on...

[jlesage]

Image manifest has been updated with recent Docker image builder (see https://github.com/docker/buildx/releases) to be in OCI format. I suspect the issue you are seeing is caused by that and your Docker version is too old to support the OCI format.

I can try to disable the provenance attestation to see if it helps. But you should definitely try to upgrade your device, since more and more images will be build the new way.

[dav1n]

Thanks. That would be appreciated for now.

And yeah - I guess I do need to look into doing a firmware update on my QNAP.

[KamikazeFighter]

I'm getting the same issue on unRAID 6.11.5 which I believe is the newest version.

[jlesage]

For unRAID it's a different issue. There is a bug with the UI that prevents fetching the correct version. You can install the "Docker Update Patch" plugin until the next version of unRAID is released.

[jlesage]

@dav1n, can you try to pull again to see if it's now working?

@KamikazeFighter, if you did not installed the patch yet, you can check if the UI now detects the version.

[dav1n]

Yes. It successfully pulls now. Thanks!!!

[jlesage]

Great, thanks for confirming !

[KamikazeFighter]

@jlesage Yeah, that fixed my problem as well. Sorry, I thought they were connected. I was only 1 version behind on this docker.

[jlesage]

Closing this issue.