Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    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
    Andy Tan
    @tanandy
    Hi guys, i just created a simple container registry from scratch and got Error status
    3 replies
    DevOps at TauRes
    @DevOps-TauRes
    We are experiencing issues with the storage when we're pushing images, we have an open ticket for this: 1516595
    PUT https://XXX.gra7.container-registry.ovh.net/v2/library/tools-XXX/blobs/uploads/72f8e4f6-6c04-4022-9a82-51f91ac29cdd?_state=REDACTED&digest=sha256%3A1064dab604aaf3f83a795daf993808926d6c578bee4ebbc16cbfb86eb4c18129: UNKNOWN: unknown error; map[DriverName:s3aws Path:/docker/registry/v2/repositories/library/tools-XXX/_uploads/72f8e4f6-6c04-4022-9a82-51f91ac29cdd/data]
    Jérémy Levilain
    @IamBlueSlime
    I have a huge number of time the unknown blob error while pushing my images. This cause my deploy pipeline to fail. If this continue I will have to leave the OVH Docker Registry cause it's just not stable enough to use in production. My pipelines are long and see them fail after 15 minutes is annoying.. I've already posted some messages here for the same issue (nov. 18 2020). Do you have isolated the issue on your side? What could you do to prevent this in the future?
    Andy Tan
    @tanandy
    hi guys, can we plug sso on harbor (DEX)? (or do you plan to support it soon ?) we would like to handle users with external oidc providers like github. Having, only local database is a problem since we want to handle users rights in a common tool
    1 reply
    Arthur Lutz
    @arthurlogilab_gitlab
    hi
    I've been told this could be a place to get support for s3/object storage ACLs... it seems this room is about the container (docker) product at OVH, am I correct ?
    5 replies
    tsn77130
    @tsn77130

    hi guys, we've got a problem with private registry, which is no more accessible (error pulling image configuration: error parsing HTTP 400 response body: invalid character '<' looking for beginning of value: "<html><h1>Bad Request</h1><p>The server could not comply with the request since it is either malformed or otherwise incorrect.</p></html>").

    could you please take a look ? (registry ID : xe1pyfka.gra5.container-registry.ovh.net)

    1 reply
    Arthur Lutz
    @arthurlogilab_gitlab
    hello, is anyone from ovh here and can answer my question ?
    Colin GILLE
    @Congelli501
    Hey, is there any progress on registry garbage collection support / fix ?
    3 replies
    Bmagic
    @bmagic
    Hello, when i want to delete a tag on my repo I have this error :
    Error occurred when to handle request in immutable handler: failed to get immutable tag rule by projectID 3, error: pq: column t0.disabled does not exist
    Anyone with the same error ?
    1 reply
    Waseem Awashra
    @wawashra
    hello why ovh Private Registry not work ?
    Colin GILLE
    @Congelli501
    Hi, we have 500 errors on image push
    received unexpected HTTP status: 500 Internal Server Error
    1 reply
    yctn
    @yctn
    i changed the Robot Token Expiration (Days) to like 3000 but exsisting robot account are not updated is this normal behavior?
    is there any way i can prevent all the current robot accounts from expiring?
    Wazabiii
    @Wazabiii
    Hi, is there any news about the upgrade to Harbor 2.x?