"fatal: failed to push layers" when trying to deploy

Replit Help
1

Love Replit, but today I cannot deploy, keep getting “fatal: failed to push layers”… Please advice how to fix and how to avoid this in the future.

Thanks

3 Likes
3

same here! I’m new to this so it could very well be my problem

1 Like
4

same. recent problem.

3 Likes
6

This looks like the same issue as Deployment issue - #6 by lincoln-replit. Over the weekend we’ve been having intermittent quota issues with our container registry. It should be back up now. Thanks for reporting!

1 Like
7

thanks for the update! giving it another shot now and hoping that all is well. seems to still be stuck on the “pulling docker image” step but I’ve only given it about 20 minutes.

edit: same issue still… here’s some info:

info: Pushing Repl layer... - 2023-05-08T16:42:04Z
info: Pushing hosting layer... - 2023-05-08T16:42:04Z
info: Retrieved cached nix layer - 2023-05-08T16:42:04Z
info: Created hosting layer - 2023-05-08T16:42:04Z
info: Created Repl layer - 2023-05-08T16:44:20Z
info: Pushing Repl (cache) layer... - 2023-05-08T16:44:20Z
info: Created Repl (cache) layer - 2023-05-08T16:44:36Z
info: Pushed image manifest - 2023-05-08T16:44:37Z
info: Pushed soci index manifest - 2023-05-08T16:44:37Z
info: Creating virtual machine - 2023-05-08T16:44:44.032Z
info: Virtual machine created - 2023-05-08T16:44:51.504Z
info: Waiting for deployment to be ready - 2023-05-08T16:44:51.585Z
info: Creating virtual machine - 2023-05-08T16:49:05.337Z
info: Virtual machine created - 2023-05-08T16:49:16.875Z
info: Waiting for deployment to be ready - 2023-05-08T16:49:16.980Z
info: Creating virtual machine - 2023-05-08T16:59:24.854Z
info: Virtual machine created - 2023-05-08T16:59:40.218Z
info: Waiting for deployment to be ready - 2023-05-08T16:59:40.285Z
info: Creating virtual machine - 2023-05-08T17:03:53.196Z
info: Virtual machine created - 2023-05-08T17:03:59.560Z
info: Waiting for deployment to be ready - 2023-05-08T17:03:59.623Z

and the logs showing the loop:

|5/8/2023, 9:49:41 AM|Starting container|
|---|---|
|5/8/2023, 9:49:38 AM|Pulling image docker-registry.replit.com/replit-user-deployments/deployments-22204423-e93deff1-f9c2-4d07-b319-7e78f1a579e3:deployments-22204423-e93deff1-f9c2-4d07-b319-7e78f1a579e3-v1683564114|
|5/8/2023, 9:45:43 AM|* Debugger PIN: 130-572-464|
|5/8/2023, 9:45:43 AM|* Debugger is active!|
|5/8/2023, 9:45:38 AM|* Restarting with stat|
|5/8/2023, 9:45:38 AM|e[31me[1mWARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.e[0m * Running on http://127.0.0.1:5000 e[33mPress CTRL+C to quite[0m|
|5/8/2023, 9:45:38 AM|* Serving Flask app 'main' * Debug mode: on|
|5/8/2023, 9:45:13 AM|Starting container|
|5/8/2023, 9:45:08 AM|Pulling image docker-registry.replit.com/replit-user-deployments/deployments-22204423-e93deff1-f9c2-4d07-b319-7e78f1a579e3:deployments-22204423-e93deff1-f9c2-4d07-b319-7e78f1a579e3-v1683564114|
1 Like
8

You need to be listening on 0.0.0.0 instead of 127.0.0.1 – we are putting out a troubleshooting guide soon with this & other tips.

2 Likes
9

thanks so much!! so glad that worked. Apologies for the noobishness, i’m learning a lot these days.

1 Like
10

Cool :slight_smile:

Please mark that answer as solution so this topic can close.

1 Like
11

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.