Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    tomasdenhouting
    @tomasdenhouting
    Hi, is there anyone from OVH available to apply the manual fix as mentioned in:
    http://travaux.ovh.net/?do=details&id=45520&
    Xavier Duthil
    @xduthil_gitlab
    Hello @tomasdenhouting, sure can you give me your registry URL in private please?
    HuguesP2s
    @HuguesP2s
    Hello, on renconte un souci avec une de nos registry. Nous n'arrivons plus a faire un push ni un pull avec cette registry. Dans notre interface Harbor, l'interface nous montre les repo et le nombre des images mais plus les images. On a un message "Project <project> not found"
    HuguesP2s
    @HuguesP2s
    quelqu'un a t'il une piste ?
    4 replies
    axelinux
    @axelinux
    Hi OVH team i have 503 error while pulling image, can someone help me please ? Many of my instance are stuck
    1 reply
    hpannetier
    @hpannetier
    Hello, my OVH docker-registry is unavailable today. I was expecting to workaround the issue by setting the Image PullPolicy to IfNotPresent in the Deployment config of my pod. But this doesn't work either. It seems that the pod is always attempting to reach the docker-registry.
    Any idea why we have this behavior? Is there another possible workaround?
    Thanks
    6 replies
    Colin GILLE
    @Congelli501
    Hi, I get some unknown blob error this morning.
    $ docker push xxxxxx.gra5.container-registry.ovh.net/xxxxxxxxxxxxx:latest
    The push refers to repository [xxxxxx.gra5.container-registry.ovh.net/xxxxxxxxxxxxx]
    1e1342d93521: Preparing
    f7a255c0ab52: Preparing
    800e62dacf38: Preparing
    1ff62ebfdf00: Preparing
    3e207b409db3: Preparing
    800e62dacf38: Layer already exists
    1ff62ebfdf00: Layer already exists
    3e207b409db3: Layer already exists
    f7a255c0ab52: Layer already exists
    unknown blob
    Thomas Garcia
    @tomgarcia__twitter
    Hello @Congelli501 , could you give me your registry url in private please ? I will have a look
    Colin GILLE
    @Congelli501
    Hi, our registry is completely down.
    We get 503 http errors for every request
    received unexpected HTTP status: 503 Service Temporarily Unavailable
    Is there anything going on ?
    2 replies
    Wouter Horré
    @wouterh
    Hi, we are migrating from docker hub and would like to replicate all our docker hub images to our OVH registry, but the replication is failing with 401 Unauthorized errors.
    3 replies
    DevOps at TauRes
    @DevOps-TauRes
    Hi, is there a timeline when the service is upgraded to Harbor 2.0 or even better 2.1?
    2 replies
    vkukk
    @vkukk
    Why does Harbour show me 0B for images and I can't delete any?
    All creation and push times are 1/1/01, 1:39 AM
    2 replies
    SebastienJardin
    @SebastienJardin
    Hi all we encounter an incident on our Control Plane the travaux is here : http://travaux.ovh.net/?do=details&id=47184
    Not all customers are impacted.
    SebastienJardin
    @SebastienJardin
    All Harbor products should works now, we are continue the investigation on our side, we let the travaux issue open for the moment.
    Sorry for the invenience
    Pierre PoF
    @neopof

    Hello, do you know where i can find the total size of my registry? In my ovh manager the size is still 0.

    I also have a question regarding an example or a doc to setup nginx front proxy pass to hide the ovh url of my registry and to make it like registry.mycompany.com. thanks in advance.

    2 replies
    DevOps at TauRes
    @DevOps-TauRes
    @SebastienJardin We're having problems with our registry, currently the web-interface is accessible, but our build jobs get timeouts when trying to connect to the registry.
    12 replies
    Baboon
    @LouisKottmann
    hello
    I get 500 Errors when pushing to our registry
    (any repository)
    Baboon
    @LouisKottmann
    it came back I can push again, this happens every now and then...
    2 replies
    Colin GILLE
    @Congelli501

    Hi, we can't push an image
    We did 5 tries from 12:04 CEST to 15:11 CEST

    The push refers to repository [xxxxxx.gra5.container-registry.ovh.net/xxxxxxxxx]
    869b88ad82bf: Preparing
    39f5759ee91a: Preparing
    9fcb4b1f6588: Preparing
    d5c7fefe9138: Preparing
    7a0035f07138: Preparing
    f567c7d48345: Preparing
    923ea7ff5381: Preparing
    b0adf2da66d5: Preparing
    66de6bafdc9e: Preparing
    90139b0092c1: Preparing
    2e3d924ff114: Preparing
    372f309d119c: Preparing
    50644c29ef5a: Preparing
    923ea7ff5381: Waiting
    b0adf2da66d5: Waiting
    50644c29ef5a: Waiting
    66de6bafdc9e: Waiting
    2e3d924ff114: Waiting
    90139b0092c1: Waiting
    372f309d119c: Waiting
    f567c7d48345: Waiting
    7a0035f07138: Layer already exists
    d5c7fefe9138: Layer already exists
    923ea7ff5381: Layer already exists
    f567c7d48345: Layer already exists
    b0adf2da66d5: Layer already exists
    66de6bafdc9e: Layer already exists
    90139b0092c1: Layer already exists
    2e3d924ff114: Layer already exists
    372f309d119c: Layer already exists
    50644c29ef5a: Layer already exists
    39f5759ee91a: Retrying in 5 seconds
    39f5759ee91a: Retrying in 4 seconds
    39f5759ee91a: Retrying in 3 seconds
    39f5759ee91a: Retrying in 2 seconds
    39f5759ee91a: Retrying in 1 second
    39f5759ee91a: Retrying in 10 seconds
    39f5759ee91a: Retrying in 9 seconds
    39f5759ee91a: Retrying in 8 seconds
    39f5759ee91a: Retrying in 7 seconds
    39f5759ee91a: Retrying in 6 seconds
    39f5759ee91a: Retrying in 5 seconds
    39f5759ee91a: Retrying in 4 seconds
    39f5759ee91a: Retrying in 3 seconds
    39f5759ee91a: Retrying in 2 seconds
    39f5759ee91a: Retrying in 1 second
    869b88ad82bf: Pushed
    9fcb4b1f6588: Pushed
    39f5759ee91a: Pushed
    received unexpected HTTP status: 500 Internal Server Error

    Is there anything going on ?

    DevOps at TauRes
    @DevOps-TauRes
    We are unable to push any images as well.
    Baboon
    @LouisKottmann
    meh, failing again, getting 500s as well
    Djangoliv
    @djangoliv
    Hello, same pb here: error pushing image: failed to push to destination ..... UNKNOWN: unknown error; map[DriverName:s3aws
    Colin GILLE
    @Congelli501
    Is there any update on this, I have 10 people waiting to push images
    DevOps at TauRes
    @DevOps-TauRes
    I just had a call with the hotline, they escalated this issue for all of us.
    Colin GILLE
    @Congelli501
    Thanks @DevOps-TauRes !
    Baboon
    @LouisKottmann
    Thanks
    Thomas Garcia
    @tomgarcia__twitter
    Hi All, we are aware about your troubles. we have problems with the storage. You can follow this issue here: http://travaux.ovh.net/?do=details&id=47499&
    MoJoce
    @MoJoce
    Hello, same pb here...
    DevOps at TauRes
    @DevOps-TauRes
    @tomgarcia__twitter Are there any updates on this? Another workday has started and our developers are in deep trouble here.
    Simon Guyennet
    @sguyennet
    Hi @DevOps-TauRes The storage issue was just updated:
    http://travaux.ovh.net/?do=details&id=47481
    Baboon
    @LouisKottmann
    it's just a scaling issue?
    Baboon
    @LouisKottmann
    the issue is still ongoing, all the pushes failed this morning...
    MoJoce
    @MoJoce
    me too
    Simon Guyennet
    @sguyennet
    Hi,
    The storage issue is currently still in investigation. Please follow the progess here:
    http://travaux.ovh.net/?do=details&id=47481
    Colin GILLE
    @Congelli501
    I confirm, push is failing again on my repo too
    Colin GILLE
    @Congelli501
    Our registry is still failing randomly, any ETA on a definitive fix?
    We are losing a lot of time retrying pipelines.
    Jérémie MONSINJON
    @jMonsinjon
    I understand and I'm really sorry...
    But no ETA from team in charge of it...
    Treussart Matthieu
    @treussart
    Hi, how can I join the notary server ? I try this : notary -s https://[id].gra7.container-registry.ovh.net/notary -d ~/.docker/trust list https://[id].gra7.container-registry.ovh.net/devops/base but I have the Go error : invalid character '<' looking for beginning of value
    10 replies
    Guilhem Bonnefille
    @gbonnefille
    Hi all, we are regularly experriencing a random push error. We are using Kaniko and the message is not really useful to diagnose:
    error pushing image: failed to push to destination xxx.gra5.container-registry.ovh.net/project/repo:tag: PUT https://xxx.gra5.container-registry.ovh.net/v2/repo/repo/blobs/uploads/a28bfac9-a522-4249-8a11-b7c8341ce79a?_state=REDACTED&digest=sha256%3A33df0b4b677132b4f20990e1443b5b8b809f2d3bf3ce22fd3c7a2ec5a36623bb: UNKNOWN: unknown error; map[DriverName:s3aws Path:/docker/registry/v2/repositories/project/repo/_upload/a28bfac9-a522-4249-8a11-b7c8341ce79a/data]
    Is it related to our usage? Does Kaniko is not safe here? I saw there is other issues related to storage. Can we consider such issue is related to global infrastructure?
    Jérémy Levilain
    @IamBlueSlime
    Same issue here with a classic Docker push. This issue is annoying in automated deployments...
    Jérémie MONSINJON
    @jMonsinjon
    @gbonnefille @IamBlueSlime
    Everything's seems OK on our side...
    Are you still in trouble? Was it a temporary downtime?
    5 replies
    DevOps at TauRes
    @DevOps-TauRes
    Hi, is there an update to the timeline when the service is upgraded to Harbor 2.0 or even better 2.1?
    3 replies
    DevOps at TauRes
    @DevOps-TauRes
    The Garbage Collection of our Harbor instance seems to be broken, "Internal Server Error". Can somebody help us?
    1 reply
    DevOps at TauRes
    @DevOps-TauRes
    We are getting more and more error when it comes to pushing images, we need help!
    error pushing image: failed to push to destination XXX.XXX.container-registry.ovh.net/library/XXX-XXX:rkYuxab: Head "https://storage.gra.cloud.ovh.net/XXX-d697-4588-bfda-eb24eaa98aa6/files/docker/registry/v2/blobs/sha256/f2/f26661f4bd05f0baedb0825bd32a7704570e64aa6f587ff7e343e8f62d4270c5/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=18677960e2d84ec482a66615d254962a%2F20210114%2FGRA%2Fs3%2Faws4_request&X-Amz-Date=20210114T080021Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=XXX": read tcp 10.42.208.30:46442->54.38.230.75:443: read: connection reset by peer
    vkukk
    @vkukk
    Registry service broken again? I can't delete old tags again.
    1 reply