Nothing to see here 😅

1

I’m trying to deploy to AMS and getting this error:

===> EXPORTING
Adding layer 'heroku/nodejs-engine:dist'
ERROR: failed to export: caching layer (sha256:794677c885fbe7334c92f9cedd9ca78256657998776725af428ab730b7e0aa49): write /launch-cache/staging/sha256:794677c885fbe7334c92f9cedd9ca78256657998776725af428ab730b7e0aa49.tar: copy_file_range: no space left on device
Error failed to fetch an image or build from source: executing lifecycle: failed with status code: 62
2

Are you using a remote builder for this deploy? If so, that out-of-space error may be caused by that. As they do get full.

If so, try fly destroy name-of-your-remote-builder. Then a new builder will be created on the next deploy, with an empty volume.

3

I don’t think so. I have Docker running locally so I presume I’m not using the remote builder?

Anyway, I destroyed the remote builder but same error:

===> EXPORTING
Adding layer 'heroku/nodejs-engine:dist'
ERROR: failed to export: caching layer (sha256:794677c885fbe7334c92f9cedd9ca78256657998776725af428ab730b7e0aa49): write /launch-cache/staging/sha256:794677c885fbe7334c92f9cedd9ca78256657998776725af428ab730b7e0aa49.tar: copy_file_range: no space left on device
Error failed to fetch an image or build from source: executing lifecycle: failed with status code: 62

This is an app that has been deployed 19 times already and I’m just pushing a minor change.

4

Is this on MacOS? You can get this error from Docker on MacOS: How to fix docker error no space left on device? | Jhooq

1 Like
5

Sorry guys. I’m a Docker idiot. I thought the error was coming from Fly.

Thanks @kurt for the link. Yeah docker system prune solved it!

2 Likes
6

I think everyone is a Docker idiot. Docker is a pain in the ass.

7 Likes