Question

App will no longer build after adding a worker

Earlier I added a worker to my app in the App Platform. I started to get errors and it wouldn’t build so I destroyed the worker. I still get the same errors now no matter what I do. It seems to be something when it is dockerizing it I think. My api has never had this problem before adding that worker, and seems to have messed everything up. Here are the errors.

[api] [2022-02-19 22:50:46] Adding 2/2 app layer(s)
[api] [2022-02-19 22:50:46] Adding layer 'launcher'
[api] [2022-02-19 22:50:46] Adding layer 'config'
[api] [2022-02-19 22:50:46] Adding label 'io.buildpacks.lifecycle.metadata'
[api] [2022-02-19 22:50:46] Adding label 'io.buildpacks.build.metadata'
[api] [2022-02-19 22:50:46] Adding label 'io.buildpacks.project.metadata'
[api] [2022-02-19 22:51:00] *** Images (sha256:(I REMOVED)):
[api] [2022-02-19 22:51:00]       <image-0> - HEAD <registry-uri-1> unexpected status code 401 Unauthorized (HEAD responses have no body, use GET for details)
[api] [2022-02-19 22:51:00] ERROR: failed to export: failed to write image to the following tags: [<image-2>: HEAD <registry-uri-3> unexpected status code 401 Unauthorized (HEAD responses have no body, use GET for details)]
[api] [2022-02-19 22:51:00] 
[api] [2022-02-19 22:51:00] command exited with code 246
[api] [2022-02-19 22:51:01]  ! Image upload failed


[api] [2022-02-19 22:55:58] 
[api] [2022-02-19 22:55:58] => Uploading the built Docker image to the container registry...
[api] [2022-02-19 22:56:00] Reusing layers from image <registry-uri-0>
[api] [2022-02-19 22:56:11] Reusing layer 'heroku/nodejs-engine:nodejs'
[api] [2022-02-19 22:56:11] ERROR: failed to export: get diff ID for previous image layer: GET https://fra1.digitaloceanspaces.com/93b2785e-b296-413b-8b29-9a6c1c52edac/docker/registry/v2/blobs/sha256/46/(I REMOVED)/data?X-Amz-Algorithm=REDACTED&X-Amz-Credential=REDACTED&X-Amz-Date=REDACTED&X-Amz-Expires=REDACTED&X-Amz-Signature=REDACTED&X-Amz-SignedHeaders=REDACTED: unexpected status code 503 Service Unavailable: upstream connect error or disconnect/reset before headers. reset reason: connection failure, transport failure reason: immediate connect error: 2
[api] [2022-02-19 22:56:11] 
[api] [2022-02-19 22:56:11] command exited with code 246
[api] [2022-02-19 22:56:12] 
[api] [2022-02-19 22:56:12] => An error occurred, trying again...

[api] [2022-02-19 23:03:29] *** Images (sha256: (I REMOVED):
[api] [2022-02-19 23:03:29]       <image-1> - HEAD <registry-uri-2> unexpected status code 401 Unauthorized (HEAD responses have no body, use GET for details)
[api] [2022-02-19 23:03:29] ERROR: failed to export: failed to write image to the following tags: [<image-3>: HEAD <registry-uri-4> unexpected status code 401 Unauthorized (HEAD responses have no body, use GET for details)]
[api] [2022-02-19 23:03:29] 
[api] [2022-02-19 23:03:29] command exited with code 246

Submit an answer


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!

Sign In or Sign Up to Answer

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.

Bobby Iliev
Site Moderator
Site Moderator badge
February 20, 2022
Accepted Answer

Hello,

This problem was most likely caused by this incident here:

https://status.digitalocean.com/incidents/nhxwxtyy76fz

As far as I can see from the error output, the App platform was not able to push the new image to the FRA1 Spaces which the incident was for.

Happy to hear that it is all working for you already!

Best,

Bobby

Went a watched an episode of Ozark, came back and forced build with clean cache again and it built.

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Become a contributor for community

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

DigitalOcean Documentation

Full documentation for every DigitalOcean product.

Resources for startups and SMBs

The Wave has everything you need to know about building a business, from raising funding to marketing your product.

Get our newsletter

Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.

New accounts only. By submitting your email you agree to our Privacy Policy

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.