Entity too large when deploying

I get the following

[Info]    Saving release...
[Error]   Deploy failed
HttpResponseError: <!DOCTYPE html>
<html lang="en">
<meta charset="utf-8">
<pre>PayloadTooLargeError: request entity too large<br> &nbsp;

Presumably its a POST size configuration somewhere or something?




Can you please elaborate on the issue? Do you have an estimation of the build size? Have you tried to push again or this happens on every push?

If possible, please share with us more details so it’s easier to understand the context.

Hi there. Been doing some more testing. Seems to fail all the time at the moment although in the past I have managed to get it to go up.

I have some build logs I’ll paste up somewhere. How do I check container sizes for you?

Hey @ajlennon,

You should be able to see more information about the builds on the Releases panel in Balena Cloud.

The reason for the failure is most likely excessive log output during the build. Can you try again with the --nologupload flag set? We do truncate logs before uploading them but we may have missed something. BTW, what CLI version is this?

Hi guys,

Apologies - I think I’ve not clarified some needed information…

I’m using OpenBalena here (hence the topic posting) so the builds are all being done locally on my own system and the failing push is pushing up to an instance of the OpenBalena server.

I kick the build off with

DEBUG=1 balena deploy does-rpi3-ros --logs --source . --emulated --build | tee build.log

Logs are

[Debug]   Parsing input...
[Debug]   Loading project...
[Debug]   Resolving project...
[Debug]   Failed to resolve project:
[Debug]   AggregateError of:
[Debug]       Error: ENOENT: no such file or directory, open '/home/ajlennon/git/does-rpi3-ros/docker-compose.yml'
[Debug]       Error: ENOENT: no such file or directory, open '/home/ajlennon/git/does-rpi3-ros/docker-compose.yaml'
[Info]    Creating default composition with source: /home/ajlennon/git/does-rpi3-ros
[Debug]   Creating project...
[Info]    Building for armv7hf/raspberrypi3
[Build]   Building services...
[Build]   main          Preparing...
[Info]    Emulation is enabled
[Debug]   Found build tasks:
[Debug]       main: build [.]
[Debug]   Resolving services with [raspberrypi3|armv7hf]
[Debug]   Found project types:
[Debug]       main: Dockerfile.template
[Debug]   Prepared tasks; building...
[Build]   main          Step 1/19 : FROM balenalib/raspberrypi3-debian:stretch-run
[Build]   main           ---> 6dafa0cd68d7
[Build]   main          Step 2/19 : COPY [".balena/qemu-execve","/tmp/qemu-execve"]
[Build]   main          <== Finished processing package [53 of 53]: 'rosbag'
[Build]   main          Removing intermediate container 8f6d0d22f94a
[Build]   main           ---> d889412ea8e8
[Build]   main          Step 18/19 : RUN ["/tmp/qemu-execve","-execve","/bin/sh","-c","echo source /opt/ros/kinetic/setup.bash >> ~/.bashrc"]
[Build]   main           ---> Running in 7f99c4c99d07
[Build]   main          Removing intermediate container 7f99c4c99d07
[Build]   main           ---> 2b1ee6625ba2
[Build]   main          Step 19/19 : CMD ./start.sh
[Build]   main           ---> Running in 540c5824fc83
[Build]   main          Removing intermediate container 540c5824fc83
[Build]   main           ---> 0cb2ea378c41
[Build]   main          Successfully built 0cb2ea378c41
[Build]   main          Successfully tagged does-rpi3-ros_main:latest
[Info]    Creating release...
[Debug]   Tagging images...
[Debug]   Authorizing push...
[Debug]   Requesting access to previously pushed image repo (v2/723ea40ed5943221675eed75ce6461a4)
[Info]    Pushing images to registry...
[Debug]   Saving image registry.spriteguard.com/v2/11a6a60f59bc268a3a501057ce3204ed
[Debug]   Untagging images...
[Info]    Saving release...
[Error]   Deploy failed

The Dockerfile it’s using is here


The CLI version is 10.1.0. I can try upgrading that…

Will also try this