Question

Build always stuck at Adding label 'io.buildpacks.project.metadata' with no other error messages

Posted October 15, 2021 419 views
Strapi

My build of strapi is always so slow that it always stuck at “Adding label ‘io.buildpacks.project.metadata’” with no other error messages

[talentlabs-cms] [2021-10-14 17:16:05] => Uploading the built Docker image to the container registry…
[talentlabs-cms] [2021-10-14 17:16:15] Adding layer 'heroku/nodejs-engine:nodejs’
[talentlabs-cms] [2021-10-14 17:16:18] Adding layer 'heroku/nodejs-engine:yarn’
[talentlabs-cms] [2021-10-14 17:17:24] Adding 2/2 app layer(s)
[talentlabs-cms] [2021-10-14 17:17:24] Adding layer 'launcher’
[talentlabs-cms] [2021-10-14 17:17:24] Adding layer 'config’
[talentlabs-cms] [2021-10-14 17:17:24] Adding label 'io.buildpacks.lifecycle.metadata’
[talentlabs-cms] [2021-10-14 17:17:24] Adding label 'io.buildpacks.build.metadata’
[talentlabs-cms] [2021-10-14 17:17:24] Adding label 'io.buildpacks.project.metadata’

3 comments

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.

×
Submit an Answer
5 answers

Hi, did you solve this problem? I am also facing this problem too!

It was fixed for some time before, but it’s happening again. I did nothing except asking support team to check.

There must be something wrong with their build system. Hope someone from DO can officially take a look in this.

This is totally unacceptable on production system (we are having our production system on DO App platform....). Thinking about migrating to another cloud provider now…

It appears to be a quirk of the buildpack container they’re using. My build succeeds (nextjs) although it takes 20+ minutes for something that takes 1-2 minutes locally. I too noticed this a week or two ago, and it then went away. @DO please keep an eye on this, like learn I am also looking to find alternative hosting solutions due to this issue.

DO really needs to fix this. Facing the same issue.