Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    bcarriou
    @bcarriou
    Hi ! Yes me
    Since two are three minutes
    Irwin Lourtet
    @ilourt
    It seems to be good now
    bcarriou
    @bcarriou
    yes it's seem be ok but it's not normal !
    I can't push from my CI to my registry:
     error pushing image: failed to push to destination 48nn886m.gra5.container-registry.ovh.net/app-dev/rocsimulator:a218c7db: UNKNOWN: unknown error; map[DriverName:s3aws Path:/docker/registry/v2/repositories/app-dev/rocsimulator/_uploads/7811c85e-b0f3-44a7-98b0-524b55e2739a/data]
    this appears frequently
    Antoine Blondeau
    @nd4pa
    hi @bcarriou, we are looking at your issue
    bcarriou
    @bcarriou
    hi @nd4pa , it's works now but sometimes it's failed alternatively
    I have again:
     error pushing image: failed to push to destination 48nn886m.gra5.container-registry.ovh.net/app/rocsimulator:4.8.0-SNAPSHOT: UNKNOWN: unknown error; map[DriverName:s3aws Path:/docker/registry/v2/repositories/app/rocsimulator/_uploads/ebe23d6e-55e6-432f-a93c-090adf6a4fa1/data]
    Antoine Blondeau
    @nd4pa
    ok, what is the size of the image you are trying to push ?
    bcarriou
    @bcarriou
    456.00MB
    Antoine Blondeau
    @nd4pa
    I did talk about this issue with a co-worker, he will look into this ASAP, (probably tommorrow)
    bcarriou
    @bcarriou
    okay thx
    bcarriou
    @bcarriou
    Hi, any news for my problem ?
    It is appears again:
     error pushing image: failed to push to destination kofmatb6.gra5.container-registry.ovh.net/app-dev/jpetstore:28f967fd: UNKNOWN: unknown error; map[DriverName:s3aws Path:/docker/registry/v2/repositories/app-dev/jpetstore/_uploads/0ce52e41-2802-4ee8-94c9-ec6563fc2e46/data]
    11 replies
    Hugo Freire Gil
    @TLmaK0
    Hi, I have problems pulling images this morning:
    3 replies
    image.png
    bcarriou
    @bcarriou
    Hi, I have sometimes failed to pull some images and the following message appears:
    Error response from daemon: received unexpected HTTP status: 500 Internal Server Error
    3 replies
    Colin GILLE
    @Congelli501
    Hi, we have 500 errors too
    Simon Guyennet
    @sguyennet
    Hi @Congelli501, Could you give me your registry ID in private please?
    Colin GILLE
    @Congelli501
    Hi, we have some errors with image push
    $ docker push xxxxxx.gra5.container-registry.ovh.net/xxxxxxx
    The push refers to repository [xxxxx.gra5.container-registry.ovh.net/xxxxxxxx
    fbfe8e4f7702: Preparing
    154d2ce96955: Preparing
    db3ffd7882fc: Preparing
    7bcf072d2d5b: Preparing
    6c536d9a40a5: Preparing
    0fec39270f4d: Preparing
    1b3ee35aacca: Preparing
    0fec39270f4d: Waiting
    6c536d9a40a5: Layer already exists
    7bcf072d2d5b: Layer already exists
    0fec39270f4d: Layer already exists
    1b3ee35aacca: Layer already exists
    fbfe8e4f7702: Pushed
    error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "<html>\r\n<head><title>404 Not Found</title></head>\r\n<body>\r\n<center><h1>404 Not Found</h1></center>\r\n<hr><center>nginx/1.17.10</center>\r\n</body>\r\n</html>\r\n"
    We just lost 20 minutes on an important fix deployment because of this error (we had to start over our build pipeline)
    Pierre PÉRONNET
    @holyhope
    Hello @Congelli501, so sorry for that lost of time. I am on it.
    Can you tell me the url of your registry please? I do not find any issue over gra5 concerning some 404 on push
    axelinux
    @axelinux
    Hi, i have issue when i'm trying to push images :
    + docker push xxxxxxxxxxx.gra5.container-registry.ovh.net/xxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxx
    The push refers to a repository [xxxxxxxxxxx.gra5.container-registry.ovh.net/xxxxxxxxxxxxxx/xxxxxxxxxxxxxxx]
    12efd09a73ba: Preparing
    610f8808e4fc: Preparing
    e5b0c49ebfe5: Waiting
    9581069bba67: Waiting
    c7afc72779d2: Retrying in 5 seconds
    36dc074069e5: Pushed
    c7afc72779d2: Retrying in 1 second
    20234c1a5aea: Pushed
    cab4466b4cc0: Pushed
    e53338b022f9: Retrying in 5 seconds
    e53338b022f9: Retrying in 4 seconds
    e53338b022f9: Retrying in 3 seconds
    e53338b022f9: Retrying in 2 seconds
    e53338b022f9: Retrying in 1 second
    f1d63970ed88: Pushed
    68707a9553cb: Pushed
    0a879da8a6d0: Pushed
    c7afc72779d2: Pushed
    unknown blob
    ERROR: script returned exit code 1
    axelinux
    @axelinux
    After multiple attempt, it's working
    erapx
    @erapx
    Hello, we keep getting the following error very often:
    "Get https://xxxxxxxxxx.gra5.container-registry.ovh.net/v2/xxxxxx/xxxxxx/manifests/latest: received unexpected HTTP status: 503 Service Temporarily Unavailable"
    this is becoming kinda annoying as it's happening quite often, I was expecting this from a beta service, tho not from a stable and gamma product
    how can we get this error not happening anymore - at least not so often - without forcing us into switching to another service?
    Thanks
    erapx
    @erapx
    @holyhope ^^ :)
    axelinux
    @axelinux
    I got the same issue as @erpax . It's very inconvenient to work with it.
    paydaycay
    @paydaycay
    Hi, I get the same issue as @erapx and @axelinux very regurarly... And now I just got a 404 Not Found on my Harbor private registry...
    Pierre PÉRONNET
    @holyhope
    Hello all, So sorry for the inconveniences. I confirm you that 503 errors may occur and be sure we are taking care of it.
    Colin GILLE
    @Congelli501
    Hey, is there something in progress on the registry ?
    I had 3 different errors in 1 hour
     7942e50a7037: Preparing
    ea35bf81cba6: Preparing
    78e27cb73bd6: Preparing
    05f3b67ed530: Preparing
    ec1817c93e7c: Preparing
    9e97312b63ff: Preparing
    e1c75a5e0bfa: Preparing
    9e97312b63ff: Waiting
    e1c75a5e0bfa: Waiting
    unauthorized: authentication required
     7942e50a7037: Preparing
    ea35bf81cba6: Preparing
    78e27cb73bd6: Preparing
    05f3b67ed530: Preparing
    ec1817c93e7c: Preparing
    9e97312b63ff: Preparing
    e1c75a5e0bfa: Preparing
    9e97312b63ff: Waiting
    e1c75a5e0bfa: Waiting
    error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "<html>\r\n<head><title>404 Not Found</title></head>\r\n<body>\r\n<center><h1>404 Not Found</h1></center>\r\n<hr><center>nginx/1.17.10</center>\r\n</body>\r\n</html>\r\n"
     bf36e14f23bf: Preparing
    b4cbda311785: Preparing
    78e27cb73bd6: Preparing
    05f3b67ed530: Preparing
    ec1817c93e7c: Preparing
    9e97312b63ff: Preparing
    e1c75a5e0bfa: Preparing
    9e97312b63ff: Waiting
    e1c75a5e0bfa: Waiting
    05f3b67ed530: Layer already exists
    ec1817c93e7c: Layer already exists
    9e97312b63ff: Layer already exists
    e1c75a5e0bfa: Layer already exists
    bf36e14f23bf: Retrying in 5 seconds
    bf36e14f23bf: Retrying in 4 seconds
    bf36e14f23bf: Retrying in 3 seconds
    bf36e14f23bf: Retrying in 2 seconds
    bf36e14f23bf: Retrying in 1 second
    unknown blob
    (Ok, I thought the previous message was sent on Friday, so ok it's taken care of)
    2 replies
    erapx
    @erapx
    @holyhope any ETA in fixing the 503s? It's very, very annoying for a production service
    Loïc
    @zoic21
    hello I can lot of different error on my registry 404, net/http: TLS handshake timeout, invalid character '<'. Is there any global issue ?
    after 10 retry it's working...
    axelinux
    @axelinux
    @zoic21 Yes i guess , @erapx @paydaycay and me have the same issue
    axelinux
    @axelinux
    BTW, i cannot see any information on this page : http://travaux.ovh.net/?project=36&status=all&perpage=50
    axelinux
    @axelinux
    @erapx , it was not there when i check, the last edited hour is 2020-06-23, 12:02 .
    Maxime Hurtrel
    @crazyman_twitter
    image.png
    Hi everyone !
    Just a quick update to let you know that :
    • The vast majority of 5XX errors root have been identified and fixed by the team. if you still experience some, do not hesitate to open a ticket so that we look into your specific case.
    • We are really happy to celebrate the graduation of Harbor by the CNCF : https://www.ovh.com/blog/celebrating-harbor-joining-the-restricted-list-of-cncf-graduated-projects/
    • To celebrate graduation, we decided to offer 2 major improvments on the Managed Private Registry offering. ( The website will be updated soon, but all existing and new customers already automatically benefit from it ):
      • M plan (40€/month) now includes vulnerability scanning
      • M plan now support up to 5TB of storage !
    paydaycay
    @paydaycay
    Hi @crazyman_twitter And for "unknown blob" errors, did you find a fix ?
    fdo13100
    @fdo13100
    Hi guys. I'm trying to access my OVH private registry and I get an error from docker login command : "Error response from daemon: login attempt to https://-----------.ovh.net/v2/ failed with status: 503 Service Unavailable"
    fdo13100
    @fdo13100
    Hi guys. I'm trying to access my OVH private registry and I get an error from docker login command : "Error response from daemon: login attempt to https://-----------.ovh.net/v2/ failed with status: 503 Service Unavailable" .
    Simon Guyennet
    @sguyennet
    Hi @fdo13100, could you send your registry ID in private please?
    Logan Mzz
    @loganmzz
    Not sure if its same issue, but I'm also unable to use helm repo update