Remote: error: file write error (No space left on device)

Product support
1

I’m getting the following error when pushing code to resin using: git push resin master

The authenticity of host 'git.resin.io (54.165.162.194)' can't be established.
ECDSA key fingerprint is SHA256:NfwmqnKId5cx1RWpebbEuuM87bCJbdyhzRnqFES9Nnw.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'git.resin.io,54.165.162.194' (ECDSA) to the list of known hosts.
Counting objects: 20, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (17/17), done.
Writing objects: 100% (20/20), 19.30 KiB | 0 bytes/s, done.
Total 20 (delta 15), reused 8 (delta 3)
remote: error: file write error (No space left on device)
remote: fatal: unable to write sha1 file
error: unpack failed: unpack-objects abnormal exit
To xxx@git.resin.io:g_xxx_xxx/xxx.git
 ! [remote rejected] master -> master (unpacker error)
error: failed to push some refs to 'g_xxx_xxx@git.resin.io:g_xxx_xxx/xxx.git'

The command was working a couple of days ago. Any ideas?

2

Looks like it’s an issue (mentioned by others on chat too). Investigating, thanks for the report!

3

@zuma - Hey! This was an intermittent issue that was fixed shortly afterwards. Please let us know if you are still seeing this.

1 Like
4

Fixed. Thanks :slight_smile:

1 Like
5

I’m trying to push an update and I’m getting a similar error message. Not sure if it’s the same issue - any tips?

[Info]     Building on ARM01
[Info]     Pulling old image for caching purposes
[Info]     Fetching base image
[==================================================>] 100%
[Info]     Building Standard Dockerfile project
[Error]    Build failed: (HTTP code 500) server error - {"message":"mkdir 
/var/lib/docker/tmp/docker-builder597425943: no space left on device"}
[Info]     Uploading successful layers to registry for caching purposes
6

+1 Please fix.

7

@MiluchOK @sheng , we have acknowledged the issue and are working on it. Please check No space left on device and https://status.resin.io for updates.

Best, Kostas

8

@MiluchOK @sheng we have performed space cleanup on the affected service in our backend and the build pipeline should be back to normal now. Please let us know if you still have any issues. We are actively looking into how to prevent this from happening again.

9

@lekkas Thanks for tracking down that issue!

1 Like
10

Hey, I’m experiencing this issue today, 5 push attemps all five end up with the same error:
remote: fatal: write error: No space left on device
error: remote unpack failed: index-pack abnormal exit
:upside_down_face:

11

Thanks for reporting this @tom .
Could you provide us some extra info about your application.
Is it a multicontainers one?
How large is the release that you are trying to push?
Are you pushing by using git push or are you using the balena CLI?

Kind regards,
Thodoris

1 Like
12

Hi @thgreasi,
Thank you for your very quick reply,

My application is single container and not more then 1Mb, I am using git push,

Best regards,
Tom

13

@thgreasi

Hi again.
Seems I deployed during an update or something because the issue is gone and the deployment log
is looking different (and better).

Thank you for your help anyway !

14

Hi @tom
We have identified an internal issue and applying a fix.
You can find more info in https://status.balena.io/ .
In case you start facing this issue again and get blocked by it, you can as a temporary workaround use the balena push or balena deploy command from the balena-cli.
Let me also point you to the respective documentation pages:
https://www.balena.io/docs/learn/deploy/deployment/#balena-push
https://www.balena.io/docs/learn/deploy/deployment/#balena-build--deploy

1 Like
15

Hi,
We have fixed the issue.
Thanks for reporting this & let us know if you face this issue again.

Kind regards,
Thodoris