Hi, is there anyone from OVH available to apply the manual fix as mentioned in:
http://travaux.ovh.net/?do=details&id=45520&
http://travaux.ovh.net/?do=details&id=45520&
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
Any idea why we have this behavior? Is there another possible workaround?
Thanks
6 replies
$ 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
Is there anything going on ?
2 replies
All creation and push times are 1/1/01, 1:39 AM
2 replies
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.
Not all customers are impacted.
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
I get 500 Errors when pushing to our registry
(any repository)
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 ErrorIs there anything going on ?
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&
Hi,
The storage issue is currently still in investigation. Please follow the progess here:
http://travaux.ovh.net/?do=details&id=47481
The storage issue is currently still in investigation. Please follow the progess here:
http://travaux.ovh.net/?do=details&id=47481
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
Hi all, we are regularly experriencing a random push error. We are using Kaniko and the message is not really useful to diagnose:
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?
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?
