# Balena-engine crashing during livepush

**URL:** <https://forums.balena.io/t/balena-engine-crashing-during-livepush/147550>\
**Category:** balenaFin\
**Tags:** raspberrypi3\
**Created:** [July 1, 2020, 8:39pm UTC](https://forums.balena.io/t/balena-engine-crashing-during-livepush/147550 "2020-07-01T20:39:18Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![alexanderkjones](https://avatars.discourse-cdn.com/v4/letter/a/ccd318/32.png) [@alexanderkjones](https://forums.balena.io/u/alexanderkjones)\
**Post date:** [July 7, 2020, 2:32pm UTC](https://forums.balena.io/t/balena-engine-crashing-during-livepush/147550/9 "2020-07-07T14:32:46Z")

</div>

For those following, @ebradbury and I have resolved this issue by replacing the source image of

`FROM balenalib/raspberrypi3-alpine-python:3.8-latest`

and instead moved to

`FROM balenalib/fincm3-python:3-stretch-run`.

This has resolved all of our issues with livepush and laggy local performance. Not clear why. Mentioning here as a cross reference to our alternate but related conversation on [https://forums.balena.io/t/is-there-a-maximum-number-allowable-containers/146698/33](https://forums.balena.io/t/is-there-a-maximum-number-allowable-containers/146698/33)

I’m not sure this is an Alpine specific issue but may be more a bug related to Alpine with livepush. Completely conjecture but wanted to bring to the Balena / Fin Team’s attention.

---

_[View the full topic](https://forums.balena.io/t/balena-engine-crashing-during-livepush/147550)._
