Local push failing : no space left on device

Product support
1

I’m trying to push a resin image onto a VM running a development download.

The docker/baleine build is failing about half way through with the following message (local paths and hostnames redacted)

$ sudo resin local push xxxxxx.local --source .
Push failed. Error: Error processing tar file(exit status 1): write xxxxxx: no space left on device Error: Error processing tar file(exit status 1): write xxxxx: no space left on device
at Stream. (/snapshot/resin-cli/node_modules/resin-sync/build/docker-utils.js:146:23)
at emitOne (events.js:96:13)
at Stream.emit (events.js:188:7)
at drain (/snapshot/resin-cli/node_modules/through/index.js:36:16)
at Stream.stream.queue.stream.push (/snapshot/resin-cli/node_modules/through/index.js:45:5)
at Parser.exports.parse.parser.onToken (/snapshot/resin-cli/node_modules/JSONStream/index.js:129:18)
at Parser.proto.write (/snapshot/resin-cli/node_modules/jsonparse/jsonparse.js:135:34)
at Stream. (/snapshot/resin-cli/node_modules/JSONStream/index.js:21:12)
at Stream.stream.write (/snapshot/resin-cli/node_modules/through/index.js:26:11)
at IncomingMessage.ondata (_stream_readable.js:555:20)
at emitOne (events.js:96:13)
at IncomingMessage.emit (events.js:188:7)
at readableAddChunk (_stream_readable.js:176:18)
at IncomingMessage.Readable.push (_stream_readable.js:134:10)
at HTTPParser.parserOnBody (_http_common.js:123:22)
at Socket.socketOnData (_http_client.js:363:20)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at readableAddChunk (_stream_readable.js:176:18)
at Socket.Readable.push (_stream_readable.js:134:10)
at TCP.onread (net.js:547:20)

Both the MacOSX host and the target device have more than 1G of free space.

The step that is failing is :slight_smile:

Step 36/41 : ADD runtime.tar.gz /

the tar file is about 77MB.

What is the limit I am hitting, and how do I increase it? Or do I need to split up the tar file?

Thanks in advance

Craig

4

Not sure what the problem was, but I deleted the resin VM virtual disk and restarted the process, and it is now working.

5

Hi @CraigStem, out of curiosity, what VM do you use for this? VirtualBox, or something else? How big disk do you set for the device?

10

I’m using VirtualBox. Both the initial non-working and subsequent working virtual drives were 32G