Docker deploy to app platform failed with error related to image

After successfull deployments, new one failed with error message

13:28:20 INFO[0020] Found cached layer, extracting to filesystem 
13:28:20 error building image: error building stage: failed to execute command: extracting fs from image: removing whiteout .wh.tmp: unlinkat //tmp: device or resource busy
13:28:20 exit status 1
13:28:20  ! Build failed (exit code 1) 

There weren’t any changes to dockerfile in project. How it could be fixed?


I’m also facing same problem while deploying my Django app. Tried more than 10 times and now I’m losing trust on DO.

This way you’re not gonna attract more customers and win big.

This comment has been deleted

Submit an 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.

This looks like an internal bug. I’m an engineer on our App Platform team and have filed a ticket to track this internally. In the mean time I recommend triggering a rebuild by using the “Deploy” button in the top right.

Same problem for me. I had to change Dockerfile RUN statement to invalidate cache layer and the next deploy was successful

If you are using the “ADD” command change it to “COPY” in your Dockerfile.

I’m having the same issue.

We’re triggering deployment from Github action, which builds docker image in our own K8S cluster, at the first time when building Docker Image and pushing to DO registry it’s okay, but from the second time it says many messages like “Layer already exists” and then starts hanging until Docker throws error “Device or Resource is Busy”.

In the beginning I was thinking it’s because my Docker daemon has some problem, but then I observe that for image with tag that built frequently, the chance it fails to upload Docker image to DO is much higher. I tried building with new tag and it’s successful in the first try

And every time I have to re-trigger job and wait until it’s successful.

Is there any update on this one? I have now triggered 10 manual deployments to no avail. This is critical for us at this point. Is there any mitigation steps we can follow?

The issue still there, any updates?

Based on the Dockerfile reference, you can specify a port in one of two ways:

ENV <key> <value> ENV <key>=<value> … Because you have spaces around =, Docker thinks you’re using the first form where your key is PORT and your value is = 8000 (which is not a number and probably why Cloud Run isn’t working).

To fix it, either specify the port without spaces (ENV PORT=8000) or without an equals sign (ENV PORT 8000).