Docker image 4.0.6 not present on repo

Get Help CMS Installation
1

Hello,
I can’t upgrade my solution.

[root@xibo-prod Xibo]# docker images ghcr.io/xibosignage/*
REPOSITORY                     TAG             IMAGE ID       CREATED         SIZE
ghcr.io/xibosignage/xibo-cms   release-3.3.8   19f9e9742a71   3 months ago    572MB
ghcr.io/xibosignage/xibo-cms   release-3.3.7   4b4db072319d   4 months ago    572MB
ghcr.io/xibosignage/xibo-xmr   0.11            5b464a45a3d8   4 months ago    638MB
ghcr.io/xibosignage/xibo-cms   release-3.3.4   1c80172d07aa   8 months ago    572MB
ghcr.io/xibosignage/xibo-xmr   0.9             03f75b423a29   21 months ago   29.5MB
[root@xibo-prod Xibo]#

I don’t see release-4.x.x

Thx for your help
Regar,

2

You need to pull that image down to see it in your local images.

If you do docker pull ghcr.io/xibosignage/release-4.0.6 you will see it, but by upping the containers it will be pulled down automatically.

3

Bonjour,
Je suis navré mais cela ne fonctionne toujours pas. Voici l’erreur que j’ai

[root@xibo-pprd Xibo]# docker pull ghcr.io/xibosignage/release-4.0.6
Using default tag: latest
Error response from daemon: Head "https://ghcr.io/v2/xibosignage/release-4.0.6/manifests/latest": denied


[root@xibo-prod Xibo]# docker inspect ghcr.io/xibosignage/xibo-cms:develop
[]
Error: No such object: ghcr.io/xibosignage/xibo-cms:develop

[root@xibo-prod Xibo]# docker inspect ghcr.io/xibosignage/xibo-cms:release-4.0.6
[]
Error: No such object: ghcr.io/xibosignage/xibo-cms:release-4.0.6

**While ghcr.io is UP**

[root@xibo-prod Xibo]# docker inspect ghcr.io/xibosignage/xibo-cms:release-3.3.8
[
    {
        "Id": "sha256:19f9e9742a710f9e36733f5e28c378e9b048cc994fe9995b6f32bf6af0e09b0a",
        "RepoTags": [
            "ghcr.io/xibosignage/xibo-cms:release-3.3.8"
        ],
        "RepoDigests": [
            "ghcr.io/xibosignage/xibo-cms@sha256:abe7f06567f2a00492976bb0594b77424a8ddd67246e9511555650f52eb55df4"
        ],
        "Parent": "",
        "Comment": "buildkit.dockerfile.v0",
        "Created": "2023-09-12T10:59:53.636798853Z",
        "Container": "",
        "ContainerConfig": {
            "Hostname": "",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,

Regar

4

Voici l’erreur que j’ai lorsque suis l’url:

https://ghcr.io/v2/xibosignage/release-4.0.6/manifests/latest

{“errors”:[{“code”:“UNAUTHORIZED”,“message”:“authentication required”}]}

5

Je ne sais pas ce que vous avez changé pour l’acces à vos dépots mais maintenant cela fonctionne.
Cordialement

6

For other that are looking at this topic, please note that we did not change anything on our side.

7

Pour les gens qui voient ce post, je n’ai absolument rien changé sur mes 3 serveurs.
J’essai depuis septembre de faire ces mises à jour, et à chaque update, aucune image Xibo v4.x de vu. Toutes les matinées, j’ai essayé docker compose -f cms_remote_mysql.yml up -d mais sans succès et vers 13H hier, mes 3 serveurs ont réussi à être mis à jour.
Maintenant j’ai ça et tout fonctionne:

[root@xibo-pprd ~]# docker images ghcr.io/xibosignage/*
REPOSITORY                     TAG             IMAGE ID       CREATED         SIZE
ghcr.io/xibosignage/xibo-cms   release-4.0.6   a8109880db73   44 hours ago    778MB
ghcr.io/xibosignage/xibo-cms   release-3.3.8   19f9e9742a71   3 months ago    572MB
ghcr.io/xibosignage/xibo-cms   release-3.3.7   4b4db072319d   4 months ago    572MB
ghcr.io/xibosignage/xibo-xmr   0.11            5b464a45a3d8   4 months ago    638MB
ghcr.io/xibosignage/xibo-cms   release-3.3.4   1c80172d07aa   8 months ago    572MB
ghcr.io/xibosignage/xibo-xmr   0.9             03f75b423a29   21 months ago   29.5MB
[root@xibo-pprd ~]#

[root@xibo-pprd ~]# docker inspect ghcr.io/xibosignage/xibo-cms:release-4.0.6
[
    {
        "Id": "sha256:a8109880db73e41d659690537ef257ee8e671d8ff360c5ccde7a9bd15253e91b",
        "RepoTags": [
            "ghcr.io/xibosignage/xibo-cms:release-4.0.6"
        ],
        "RepoDigests": [
            "ghcr.io/xibosignage/xibo-cms@sha256:0bee04a703b17cf0e880336da504d4a3f6954d3933f8690c6a5519bb97a3c34e"
        ],
        "Parent": "",
        "Comment": "buildkit.dockerfile.v0",
        "Created": "2023-12-12T10:27:24.687297931Z",

Cordialement,

8

That is so strange!

You changed nothing, we changed nothing, so I can only assume that GitHub changed something. Perhaps they had an issue with the container registry which has now been solved.

1 Like
9

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.