Report this

What is the reason for this report?

Timouts building app platform worker

Posted on October 16, 2020

I was attempting to build my first app platform worker using docker. This is a celery worker. On the final step of the build (which took nearly 20 mins) I get a timeout error from the pushing of the image to the registry. Here are the last bits of the log

 18:43:39 INFO[0378] Pushing layer <registry-uri> to cache now 
 18:43:39 INFO[0378] ENTRYPOINT [ "celery", "worker", "-A", "celery_server", "--loglevel=info" ] 
 18:43:39 INFO[0378] No files changed in this command, skipping snapshotting. 
 18:52:02 WARN[0881] error uploading layer to cache: failed to push to destination <registry-uri> PATCH https://<registry-uri> unsupported status code 524; body: <html>
 18:52:02 <head><title>524 Origin Time-out</title></head>
 18:52:02 <body bgcolor="white">
 18:52:02 <center><h1>524 Origin Time-out</h1></center>
 18:52:02 <hr><center>cloudflare-nginx</center>
 18:52:02 </body>
 upertech-engine | 18:52:02 </html>
 19:00:49 error pushing image: failed to push to destination <image>: PATCH https://<registry-uri> unsupported status code 524; body: <html>
 19:00:49 <head><title>524 Origin Time-out</title></head>
 19:00:49 <body bgcolor="white">
 19:00:49 <center><h1>524 Origin Time-out</h1></center>
 19:00:49 <hr><center>cloudflare-nginx</center>
 19:00:49 </body>
 19:00:49 </html>
 19:00:49 
 19:00:49 exit status 1

Curious about the registry being used, I assumed it is the DO container registry. So I decided to try building the docker image locally and pushing it to the registry. After a long while, I got the same error code 524.

Is there a limit to how large a layer can be? Has anyone else seen this issue?

For the record the official dockerhub never had an issue when pushing this docker image to it.



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

I have the same problem during deploy app rendering | 03:43:34 Adding layer ‘launcher’ rendering | 03:43:34 Adding layer ‘heroku/python:profile’ rendering | 03:43:34 Adding 1/1 app layer(s) rendering | 03:43:34 Adding layer ‘config’ rendering | 03:43:34 *** Images (sha256:d6c5339af42210dd2cb41b93e18c254c66395d2c74a4ffd2d3f3bda4716c649d): rendering | 03:43:34 <image> - PATCH https://<registry-uri> unsupported status code 524; body: <html> rendering | 03:43:34 <head><title>524 Origin Time-out</title></head> rendering | 03:43:34 <body bgcolor=“white”> rendering | 03:43:34 <center><h1>524 Origin Time-out</h1></center> rendering | 03:43:34 <hr><center>cloudflare-nginx</center> rendering | 03:43:34 </body> rendering | 03:43:34 </html>

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.