[GH-ISSUE #1215] Manifest for karakeep-workers:0.23.1 is broken. #792

Closed
opened 2026-03-02 11:52:45 +03:00 by kerem · 2 comments
Owner

Originally created by @jeraldcheong on GitHub (Apr 7, 2025).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1215

Describe the Bug

When using docker containers, it looks like the manifest for karakeep-workers:0.23.1 is broken while karakeep:0.23.1 works.

Steps to Reproduce

❯ docker pull ghcr.io/karakeep-app/karakeep-workers:v0.23.1
Error response from daemon: manifest unknown

Expected Behaviour

❯ docker image rm ghcr.io/karakeep-app/karakeep-workers:latest
Untagged: ghcr.io/karakeep-app/karakeep-workers:latest
Untagged: ghcr.io/karakeep-app/karakeep-workers@sha256:77331b97143b405551e02d2c1c9320c1068a925d3129b1c743a277059770b0f3
Deleted: sha256:5e2dd72a563e95d8c57c76efc52aaa5be405ab31bda1f52ec350c77bf2a71674
Deleted: sha256:2616d8c6835c2792e43a2512dc2cdc900531fe7b6cd9f63227b46f67427b64a5
Deleted: sha256:25241e902f3de8103b97148129a26d854e87d0b556f1329137673a22e19ff8dc
Deleted: sha256:5e78db048463ca5a9b939f8e7c53bcdb43e7c893c6cb268a725d0d22a534d8dc
Deleted: sha256:6b7f7a646be134fc1001516d45facd75edc6658f86892b63fad79779ad16ac2f
Deleted: sha256:2175a14e300aa9a76fe541365f3791fb1a9594148b668dea5d1f85c0f69a60ef
Deleted: sha256:9e1a3d39f8580f2dc9adaa3d9929ab3e2f0a81c435b5cb4c93fd775c565075f9
Deleted: sha256:a8b8c8634d8372a094123f3c7867b8142df1e5c455436f47eee2bb47fa5f05f1
Deleted: sha256:465dc62c0c1650011ba61ba4eca4cd51e7373e4441b472c56c803e0cad20424c
Deleted: sha256:bd06ff8357e7cfcb6b964e7d4ad05524aa6db8bdea0d38f0c40a5dced461277c
Deleted: sha256:453131d7dda355780e56fb987a9d6a80183cf0ae3ee61d32f5638fb5e0ed3e2c
Deleted: sha256:b74cbeb3f752b2cc309d04b3f80c4871010371aba8206b4053c13b04f479c4f5

Screenshots or Additional Context

No response

Device Details

No response

Exact Hoarder Version

0.23.1

Have you checked the troubleshooting guide?

  • I have checked the troubleshooting guide and I haven't found a solution to my problem
Originally created by @jeraldcheong on GitHub (Apr 7, 2025). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1215 ### Describe the Bug When using docker containers, it looks like the manifest for karakeep-workers:0.23.1 is broken while karakeep:0.23.1 works. ### Steps to Reproduce ❯ docker pull ghcr.io/karakeep-app/karakeep-workers:v0.23.1 Error response from daemon: manifest unknown ### Expected Behaviour ❯ docker image rm ghcr.io/karakeep-app/karakeep-workers:latest Untagged: ghcr.io/karakeep-app/karakeep-workers:latest Untagged: ghcr.io/karakeep-app/karakeep-workers@sha256:77331b97143b405551e02d2c1c9320c1068a925d3129b1c743a277059770b0f3 Deleted: sha256:5e2dd72a563e95d8c57c76efc52aaa5be405ab31bda1f52ec350c77bf2a71674 Deleted: sha256:2616d8c6835c2792e43a2512dc2cdc900531fe7b6cd9f63227b46f67427b64a5 Deleted: sha256:25241e902f3de8103b97148129a26d854e87d0b556f1329137673a22e19ff8dc Deleted: sha256:5e78db048463ca5a9b939f8e7c53bcdb43e7c893c6cb268a725d0d22a534d8dc Deleted: sha256:6b7f7a646be134fc1001516d45facd75edc6658f86892b63fad79779ad16ac2f Deleted: sha256:2175a14e300aa9a76fe541365f3791fb1a9594148b668dea5d1f85c0f69a60ef Deleted: sha256:9e1a3d39f8580f2dc9adaa3d9929ab3e2f0a81c435b5cb4c93fd775c565075f9 Deleted: sha256:a8b8c8634d8372a094123f3c7867b8142df1e5c455436f47eee2bb47fa5f05f1 Deleted: sha256:465dc62c0c1650011ba61ba4eca4cd51e7373e4441b472c56c803e0cad20424c Deleted: sha256:bd06ff8357e7cfcb6b964e7d4ad05524aa6db8bdea0d38f0c40a5dced461277c Deleted: sha256:453131d7dda355780e56fb987a9d6a80183cf0ae3ee61d32f5638fb5e0ed3e2c Deleted: sha256:b74cbeb3f752b2cc309d04b3f80c4871010371aba8206b4053c13b04f479c4f5 ### Screenshots or Additional Context _No response_ ### Device Details _No response_ ### Exact Hoarder Version 0.23.1 ### Have you checked the troubleshooting guide? - [x] I have checked the troubleshooting guide and I haven't found a solution to my problem
kerem 2026-03-02 11:52:45 +03:00
Author
Owner

@MohamedBassem commented on GitHub (Apr 7, 2025):

Hey, upgrading to 0.23.2 should solve this. Also consider moving from the legacy separate containers by following this guide here: https://docs.karakeep.app/Guides/legacy-container-upgrade

<!-- gh-comment-id:2783393475 --> @MohamedBassem commented on GitHub (Apr 7, 2025): Hey, upgrading to `0.23.2` should solve this. Also consider moving from the legacy separate containers by following this guide here: https://docs.karakeep.app/Guides/legacy-container-upgrade
Author
Owner

@jeraldcheong commented on GitHub (Apr 8, 2025):

Thank you for this Mohamed!

Also, thank you for sharing the link. I have migrated away from legacy separate containers.

<!-- gh-comment-id:2785211497 --> @jeraldcheong commented on GitHub (Apr 8, 2025): Thank you for this Mohamed! Also, thank you for sharing the link. I have migrated away from legacy separate containers.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/karakeep#792
No description provided.