Pushing of Docker Images fails

RenkuLab
1

As you can see the build is successful, but the pushing of the image fails at the pushing of certain layers (timeout of RenkuLab connection?):

Successfully built db5b1140647a
Successfully tagged registry.renkulab.io/*-pathfinder/base_images/base:build
$ docker push $BASE_NAME:build
The push refers to repository [registry.renkulab.io/*-pathfinder/base_images/base]
589e6d6e4135: Preparing
ed21e49e92f5: Preparing
8c64adab6c07: Preparing
5ac841417fd1: Preparing
9a5c4aaac6a5: Preparing
fee55ab0a1f3: Preparing
64090f1ab73a: Preparing
7d83f0d43502: Preparing
3d40c0a49003: Preparing
b3b536af4d33: Preparing
f68ef921efae: Preparing
64090f1ab73a: Waiting
7d83f0d43502: Waiting
3d40c0a49003: Waiting
b3b536af4d33: Waiting
fee55ab0a1f3: Waiting
9a5c4aaac6a5: Layer already exists
5ac841417fd1: Layer already exists
8c64adab6c07: Pushed
fee55ab0a1f3: Layer already exists
64090f1ab73a: Layer already exists
7d83f0d43502: Layer already exists
3d40c0a49003: Layer already exists
b3b536af4d33: Layer already exists
f68ef921efae: Layer already exists
ed21e49e92f5: Pushed
589e6d6e4135: Retrying in 5 seconds
589e6d6e4135: Retrying in 4 seconds
589e6d6e4135: Retrying in 3 seconds
589e6d6e4135: Retrying in 2 seconds
589e6d6e4135: Retrying in 1 second
589e6d6e4135: Retrying in 10 seconds
589e6d6e4135: Retrying in 9 seconds
589e6d6e4135: Retrying in 8 seconds
589e6d6e4135: Retrying in 7 seconds
589e6d6e4135: Retrying in 6 seconds
589e6d6e4135: Retrying in 5 seconds
589e6d6e4135: Retrying in 4 seconds
589e6d6e4135: Retrying in 3 seconds
589e6d6e4135: Retrying in 2 seconds
589e6d6e4135: Retrying in 1 second
589e6d6e4135: Retrying in 15 seconds
589e6d6e4135: Retrying in 14 seconds
589e6d6e4135: Retrying in 13 seconds
589e6d6e4135: Retrying in 12 seconds
589e6d6e4135: Retrying in 11 seconds
589e6d6e4135: Retrying in 10 seconds
589e6d6e4135: Retrying in 9 seconds
589e6d6e4135: Retrying in 8 seconds
589e6d6e4135: Retrying in 7 seconds
589e6d6e4135: Retrying in 6 seconds
589e6d6e4135: Retrying in 5 seconds
589e6d6e4135: Retrying in 4 seconds
589e6d6e4135: Retrying in 3 seconds
589e6d6e4135: Retrying in 2 seconds
589e6d6e4135: Retrying in 1 second
589e6d6e4135: Retrying in 20 seconds
589e6d6e4135: Retrying in 19 seconds
589e6d6e4135: Retrying in 18 seconds
589e6d6e4135: Retrying in 17 seconds
589e6d6e4135: Retrying in 16 seconds
589e6d6e4135: Retrying in 15 seconds
589e6d6e4135: Retrying in 14 seconds
589e6d6e4135: Retrying in 13 seconds
589e6d6e4135: Retrying in 12 seconds
589e6d6e4135: Retrying in 11 seconds
589e6d6e4135: Retrying in 10 seconds
589e6d6e4135: Retrying in 9 seconds
589e6d6e4135: Retrying in 8 seconds
589e6d6e4135: Retrying in 7 seconds
589e6d6e4135: Retrying in 6 seconds
589e6d6e4135: Retrying in 5 seconds
589e6d6e4135: Retrying in 4 seconds
589e6d6e4135: Retrying in 3 seconds
589e6d6e4135: Retrying in 2 seconds
589e6d6e4135: Retrying in 1 second
2

Hi @pascal.baumann thanks for reporting this - did you try triggering the build again and did it succeed?

3

Hi @rrrrrok, thank you for your reply - sadly not, I got now multiple other pipelines also failing. I will give you sufficient rights to access the private group. May it hopefully help the investigation on your side.

4

@pascal.baumann these problems are occurring because of problems with our cloud provider (which are out of our control). They seem to have been fixed now so if you retry you should be able to build your images. We will monitor the situation and examine things further.

2 Likes
5

I see, thank you for your update. I will run the pipelines again, and will notify you of any changes.

6

Issue still persists =(

Successfully built 0218c3991f52
Successfully tagged registry.renkulab.io/*-pathfinder/base_images/base:build
$ docker push $BASE_NAME:build
The push refers to repository [registry.renkulab.io/*-pathfinder/base_images/base]
0e99beb2ee18: Preparing
e5c8ac87cfff: Preparing
8ec2967530cd: Preparing
5ac841417fd1: Preparing
9a5c4aaac6a5: Preparing
fee55ab0a1f3: Preparing
64090f1ab73a: Preparing
7d83f0d43502: Preparing
3d40c0a49003: Preparing
b3b536af4d33: Preparing
f68ef921efae: Preparing
fee55ab0a1f3: Waiting
64090f1ab73a: Waiting
3d40c0a49003: Waiting
7d83f0d43502: Waiting
b3b536af4d33: Waiting
f68ef921efae: Waiting
9a5c4aaac6a5: Layer already exists
5ac841417fd1: Layer already exists
fee55ab0a1f3: Layer already exists
64090f1ab73a: Layer already exists
8ec2967530cd: Pushed
7d83f0d43502: Layer already exists
3d40c0a49003: Layer already exists
b3b536af4d33: Layer already exists
f68ef921efae: Layer already exists
e5c8ac87cfff: Pushed
0e99beb2ee18: Retrying in 5 seconds
0e99beb2ee18: Retrying in 4 seconds
0e99beb2ee18: Retrying in 3 seconds
0e99beb2ee18: Retrying in 2 seconds
0e99beb2ee18: Retrying in 1 second
0e99beb2ee18: Retrying in 10 seconds
0e99beb2ee18: Retrying in 9 seconds
0e99beb2ee18: Retrying in 8 seconds
0e99beb2ee18: Retrying in 7 seconds
0e99beb2ee18: Retrying in 6 seconds
0e99beb2ee18: Retrying in 5 seconds
0e99beb2ee18: Retrying in 4 seconds
0e99beb2ee18: Retrying in 3 seconds
0e99beb2ee18: Retrying in 2 seconds
0e99beb2ee18: Retrying in 1 second
7

I forked your project and moved a few things around in the CI file (though I don’t think that had any real effect) but now the build passed. Still a bunch of retries, the cause of which is not really clear to me. I think that python layer at the end is quite large, so that might be resulting in some failures.