# balenaEngine fails on Raspbian

**URL:** <https://forums.balena.io/t/balenaengine-fails-on-raspbian/96249>\
**Category:** balenaEngine\
**Created:** [April 20, 2020, 8:02pm UTC](https://forums.balena.io/t/balenaengine-fails-on-raspbian/96249 "2020-04-20T20:02:24Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![kirchhof](https://avatars.discourse-cdn.com/v4/letter/k/ce7236/32.png) [@kirchhof](https://forums.balena.io/u/kirchhof)\
**Post date:** [April 20, 2020, 8:02pm UTC](https://forums.balena.io/t/balenaengine-fails-on-raspbian/96249/1 "2020-04-20T20:02:24Z")

</div>

Hello everyone,

if I install the balenaEngine on Raspbian, running any image fails. Do you know how to solve this issue?

### Steps to reproduce:

1. Flash Raspbian on a micro SD card using the [Raspberry Pi Imager](https://www.raspberrypi.org/downloads/) (Raspbian Release 2020-02-13)
2. Add an empty file called SSH to the micro SD card to enable SSH
3. Insert the SD card into a Raspberry Pi 4 and connect using SSH (credentials: User: pi, Password: raspberry)
4. For skipping authentication, log in as root using `sudo -i`
5. Install balenaEngine by running `curl -sfL https://balena.io/engine/install.sh | sh`
6. Start the demon (backgrounded) using `balena-engine-daemon &` (see [this post](https://forums.balena.io/t/install-balena-engine-to-raspbian/36856))
7. Try to run an image: `balena-engine run armhf/hello-world` ([Docker Hub](https://hub.docker.com/r/armhf/hello-world))

### Expected Results:

A “Hello World” text should be printed to the terminal. Similar to the one produced by Docker’s official hello-world image.

### Actual results:

```auto
root@raspberrypi:~# balena-engine run armhf/hello-world
INFO[2020-04-20T14:55:07.086962609+01:00] ignoring event module=libcontainerd namespace=moby topic=/containers/create type="*events.ContainerCreate"
INFO[0132] shim balena-engine-containerd-shim started address=/containerd-shim/moby/348e13e3da036faa15b398625aa21a97efa23c5ce79ba3aa5d4799b7727f64d5/shim.sock debug=false module=containerd/tasks pid=901
INFO[0132] shim reaped id=348e13e3da036faa15b398625aa21a97efa23c5ce79ba3aa5d4799b7727f64d5 module=containerd/tasks
INFO[2020-04-20T14:55:07.603121457+01:00] ignoring event module=libcontainerd namespace=moby topic=/containers/delete type="*events.ContainerDelete"
ERRO[2020-04-20T14:55:08.116249750+01:00] 348e13e3da036faa15b398625aa21a97efa23c5ce79ba3aa5d4799b7727f64d5 cleanup: failed to delete container from containerd: no such container 
ERRO[2020-04-20T14:55:08.116375027+01:00] Handler for POST /v1.35/containers/348e13e3da036faa15b398625aa21a97efa23c5ce79ba3aa5d4799b7727f64d5/start returned error: unable to find "net_prio" in controller set: unknown 
balena-engine: Error response from daemon: unable to find "net_prio" in controller set: unknown.
ERRO[0001] error waiting for container: context canceled 

```

### Notes:

I checked that the image works as expected if I connect to a Raspberry Pi running balenaOS through the webconsole provided by the balenaCloud. The error only occurs it I install balenaEngine on Raspbian. The balenaEngine on Raspbian also fails for images provided by the balenalib, e.g. `balena-engine run -it balenalib/raspberrypi4-64-alpine /bin/bash`.

---

<div class="post-metadata">

**Author:** ![dtischler](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/dtischler/32/2483_2.png) [@dtischler](https://forums.balena.io/u/dtischler)\
**Post date:** [April 20, 2020, 9:11pm UTC](https://forums.balena.io/t/balenaengine-fails-on-raspbian/96249/3 "2020-04-20T21:11:36Z")

</div>

Hello Christian, thanks for the detailed note and troubleshooting!

Looking at that error, it seems that it may be related to this issue: [https://github.com/docker/for-linux/issues/545](https://github.com/docker/for-linux/issues/545)

The solutions, according to those comments, is to downgrade systemd (seems the error began appearing at version 240), or to recompile the kernel with CONFIG\_CGROUP\_NET\_PRIO enabled.

I have pinged the balenaEngine maintainer though, to see if there is anything else that we can do to work around the issue. Thanks!

---

<div class="post-metadata">

**Author:** ![kirchhof](https://avatars.discourse-cdn.com/v4/letter/k/ce7236/32.png) [@kirchhof](https://forums.balena.io/u/kirchhof)\
**Post date:** [April 21, 2020, 6:54am UTC](https://forums.balena.io/t/balenaengine-fails-on-raspbian/96249/5 "2020-04-21T06:54:14Z")

</div>

Thank you for the suggestion. Since the images work as expected using a current version of Docker, I hoped this could be fixed by updating or fixing the balenaEngine.

I’m not really a big fan of downgrading systemd or recompiling the kernel. Downgrading parts of the system may always cause new side effects and due to the current Corona crisis, I unfortunately have no easy physical access to most of my devices, which means reflashing the SD cards with a self-compiled kernel is not really an option for me.

---

<div class="post-metadata">

**Author:** ![Vitaliy](https://avatars.discourse-cdn.com/v4/letter/v/4bbf92/32.png) [@Vitaliy](https://forums.balena.io/u/Vitaliy)\
**Post date:** [September 12, 2020, 1:40pm UTC](https://forums.balena.io/t/balenaengine-fails-on-raspbian/96249/7 "2020-09-12T13:40:35Z")

</div>

I confirm the same issue.  
Running latest version of plain docker on Raspbian works as expected.  
Running latest version of balena-Engine fails with:

> balena-engine: Error response from daemon: unable to find “net\_prio” in controller set: unknown.  
> ERRO[0001] error waiting for container: context canceled

This issue had been resolved for docker a year ago, as you may see in the same issue report:

> <https://github.com/docker/for-linux/issues/545>
>
> \<!--
> This issue tracker is for \*bug reports\* and \*feature requests\*.
> For quest…ions, and getting help on using docker:
> 
> \- Docker documentation - https://docs.docker.com
> \- Docker Forums - https://forums.docker.com
> \- Docker community Slack - https://dockercommunity.slack.com/ (register here: http://dockr.ly/community)
> \- Post a question on StackOverflow, using the Docker tag
> \--\>
> 
> \* \[x\] This is a bug report
> \* \[\] This is a feature request
> \* \[x\] I searched existing issues before opening this one
> 
> \<!--
> DO NOT report security issues publicly! If you suspect you discovered
> a security issue, send your report privately to security@docker.com.
> \--\>
> 
> \### Expected behavior
> Create and run containers.
> 
> \### Actual behavior
> \`\`\`
> \# docker run --rm -it alpine:3.8 /bin/sh
> docker: Error response from daemon: unable to find "net\_prio" in controller set: unknown.
> \`\`\`
> 
> \### Steps to reproduce the behavior
> 
> \<!--
> Describe the exact steps to reproduce. If possible, provide a \*minimum\*
> reproduction example; take into account that others do not have access
> to your private images, source code, and environment.
> 
> REMOVE SENSITIVE DATA BEFORE POSTING (replace those parts with "REDACTED")
> \--\>
> 
> \*\*Output of \`docker version\`:\*\*
> 
> \`\`\`
> Client:
> Version: 18.09.0
> API version: 1.39
> Go version: go1.10.4
> Git commit: 4d60db4
> Built: Wed Nov 7 00:57:21 2018
> OS/Arch: linux/arm
> Experimental: false
> 
> Server: Docker Engine - Community
> Engine:
> Version: 18.09.0
> API version: 1.39 (minimum version 1.12)
> Go version: go1.10.4
> Git commit: 4d60db4
> Built: Wed Nov 7 00:17:57 2018
> OS/Arch: linux/arm
> Experimental: true
> \`\`\`
> 
> \*\*Output of \`docker info\`:\*\*
> 
> \`\`\`
> Containers: 0
> Running: 0
> Paused: 0
> Stopped: 0
> Images: 5
> Server Version: 18.09.0
> Storage Driver: btrfs
> Build Version: Btrfs v4.7.3
> Library Version: 101
> Logging Driver: json-file
> Cgroup Driver: cgroupfs
> Plugins:
> Volume: local
> Network: bridge host ipvlan macvlan null overlay
> Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
> Swarm: active
> NodeID: jxgj5lhwlq7mep5e4jqx64frm
> Is Manager: true
> ClusterID: m10pfu1k75j8mvx5mqxjbb67n
> Managers: 3
> Nodes: 5
> Default Address Pool: 10.0.0.0/8
> SubnetSize: 24
> Orchestration:
> Task History Retention Limit: 5
> Raft:
> Snapshot Interval: 10000
> Number of Old Snapshots to Retain: 0
> Heartbeat Tick: 1
> Election Tick: 3
> Dispatcher:
> Heartbeat Period: 5 seconds
> CA Configuration:
> Expiry Duration: 3 months
> Force Rotate: 0
> Autolock Managers: false
> Root Rotation In Progress: false
> Node Address: 192.168.1.37
> Manager Addresses:
> 192.168.1.33:2377
> 192.168.1.34:2377
> 192.168.1.37:2377
> Runtimes: runc
> Default Runtime: runc
> Init Binary: docker-init
> containerd version: c4446665cb9c30056f4998ed953e6d4ff22c7c39
> runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
> init version: fec3683
> Security Options:
> seccomp
> Profile: default
> Kernel Version: 4.19.13-v7+
> Operating System: Raspbian GNU/Linux buster/sid
> OSType: linux
> Architecture: armv7l
> CPUs: 4
> Total Memory: 926.1MiB
> Name: docker02
> ID: KCJI:V4QV:M3ZZ:R5IU:R444:GNAX:3ORW:CEDK:V367:6X27:OHXC:VCVB
> Docker Root Dir: /var/lib/docker
> Debug Mode (client): false
> Debug Mode (server): false
> Registry: https://index.docker.io/v1/
> Labels:
> Experimental: true
> Insecure Registries:
> 127.0.0.0/8
> Live Restore Enabled: false
> Product License: Community Engine
> 
> WARNING: No swap limit support
> WARNING: No cpu cfs quota support
> WARNING: No cpu cfs period support
> \`\`\`
> 
> \*\*Additional environment details (AWS, VirtualBox, physical, etc.)\*\*
> 
> I use Raspbian buster with the latest kernel (branch next) : \`Linux docker02 4.19.13-v7+ #1186 SMP Tue Jan 1 11:32:58 GMT 2019 armv7l GNU/Linux\`.
> 
> Everything was working fine but since the last upgrade (of Raspbian), it seems to be broken.
> 
> \`\`\`
> \# ls -hl /sys/fs/cgroup/
> total 0
> dr-xr-xr-x 5 root root 0 Dec 21 19:53 blkio
> lrwxrwxrwx 1 root root 11 Dec 21 19:53 cpu -\> cpu,cpuacct
> lrwxrwxrwx 1 root root 11 Dec 21 19:53 cpuacct -\> cpu,cpuacct
> dr-xr-xr-x 5 root root 0 Dec 21 19:53 cpu,cpuacct
> dr-xr-xr-x 3 root root 0 Dec 21 19:53 cpuset
> dr-xr-xr-x 5 root root 0 Dec 21 19:53 devices
> dr-xr-xr-x 3 root root 0 Dec 21 19:53 freezer
> dr-xr-xr-x 5 root root 0 Dec 21 19:53 memory
> dr-xr-xr-x 3 root root 0 Dec 21 19:53 net\_cls
> lrwxrwxrwx 1 root root 7 Dec 21 19:53 net\_prio -\> net\_cls
> dr-xr-xr-x 6 root root 0 Dec 21 19:53 systemd
> dr-xr-xr-x 5 root root 0 Dec 21 19:53 unified
> \`\`\`
> 
> \`\`\`
> \# mount | grep cgroup
> tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
> cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
> cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
> cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
> cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
> cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
> cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
> cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
> cgroup on /sys/fs/cgroup/net\_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net\_cls)
> cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
> \`\`\`
> 
> Do you have any ideas or tests i can do ?
> Regards.
> 
> Thanks,

When do you expect to port the fix to balenaEngine?

---

<div class="post-metadata">

**Author:** ![jairo](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/jairo/32/4743_2.png) [@jairo](https://forums.balena.io/u/jairo)\
**Post date:** [October 16, 2020, 7:57pm UTC](https://forums.balena.io/t/balenaengine-fails-on-raspbian/96249/8 "2020-10-16T19:57:49Z")

</div>

Guys, do we have a solution to this issue?

---

<div class="post-metadata">

**Author:** ![jairo](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/jairo/32/4743_2.png) [@jairo](https://forums.balena.io/u/jairo)\
**Post date:** [October 19, 2020, 3:06pm UTC](https://forums.balena.io/t/balenaengine-fails-on-raspbian/96249/12 "2020-10-19T15:06:27Z")

</div>

A small update here, guys. I noticed that balena-engine have new releases in the github page ([https://github.com/balena-os/balena-engine/releases/tag/v18.9.13](https://github.com/balena-os/balena-engine/releases/tag/v18.9.13)). I just test that one and it worked nicely!! Maybe that can be a solution to you too, @Vitaliy? 😉

Maybe it’s a good thing to update this page to the latest release? [https://www.balena.io/engine/](https://www.balena.io/engine/)

---

<div class="post-metadata">

**Author:** ![JuanFRidano](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/juanfridano/32/3934_2.png) [@JuanFRidano](https://forums.balena.io/u/JuanFRidano)\
**Post date:** [October 19, 2020, 3:35pm UTC](https://forums.balena.io/t/balenaengine-fails-on-raspbian/96249/14 "2020-10-19T15:35:46Z")

</div>

Hello Jairo,

Thank you for pointing that out, v17.12.0 is definitely not the latest release and it should be updated, we will be updating it now on the website  
Glad that the upgrade worked for you

best regards,

Juan

---

<div class="post-metadata">

**Author:** ![Vitaliy](https://avatars.discourse-cdn.com/v4/letter/v/4bbf92/32.png) [@Vitaliy](https://forums.balena.io/u/Vitaliy)\
**Post date:** [October 29, 2020, 4:53pm UTC](https://forums.balena.io/t/balenaengine-fails-on-raspbian/96249/16 "2020-10-29T16:53:58Z")

</div>

with 18.9.13 i still get the same error:  
balena-engine: Error response from daemon: unable to find “net\_prio” in controller set: unknown.

Are you running it with --network=host ?

---

<div class="post-metadata">

**Author:** ![robertgzr](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/robertgzr/32/1387_2.png) [@robertgzr](https://forums.balena.io/u/robertgzr)\
**Post date:** [October 29, 2020, 5:04pm UTC](https://forums.balena.io/t/balenaengine-fails-on-raspbian/96249/17 "2020-10-29T17:04:24Z")

</div>

hm this sounds like [https://github.com/docker/for-linux/issues/545](https://github.com/docker/for-linux/issues/545)  
which should be fixed since balena-engine 18.09.6

what version of systemd are you running?

---

<div class="post-metadata">

**Author:** ![jairo](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/jairo/32/4743_2.png) [@jairo](https://forums.balena.io/u/jairo)\
**Post date:** [October 30, 2020, 2:51pm UTC](https://forums.balena.io/t/balenaengine-fails-on-raspbian/96249/20 "2020-10-30T14:51:15Z")

</div>

Are you sure? I think I got the error before reloading the daemon or something like that. Maybe try restarting the system just to move that possibility out of the way?

---

<div class="post-metadata">

**Author:** ![jtonello](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/jtonello/32/3246_2.png) [@jtonello](https://forums.balena.io/u/jtonello)\
**Post date:** [October 30, 2020, 6:34pm UTC](https://forums.balena.io/t/balenaengine-fails-on-raspbian/96249/21 "2020-10-30T18:34:38Z")

</div>

Hi Jairo,

Can you confirm your version of `systemd`? if it’s 420, that’s a known issue that was corrected with the newer version of balenaEngine 18.09.6.

John

---

<div class="post-metadata">

**Author:** ![xginn8](https://avatars.discourse-cdn.com/v4/letter/x/8baadc/32.png) [@xginn8](https://forums.balena.io/u/xginn8)\
**Post date:** [November 20, 2020, 4:51pm UTC](https://forums.balena.io/t/balenaengine-fails-on-raspbian/96249/23 "2020-11-20T16:51:34Z")

</div>

Hi there,

Just wanted to check in again and see if you were able to check that version or not. Please do let us know!

---

<div class="post-metadata">

**Author:** ![clementine](https://avatars.discourse-cdn.com/v4/letter/c/8dc957/32.png) [@clementine](https://forums.balena.io/u/clementine)\
**Post date:** [November 24, 2020, 8:28am UTC](https://forums.balena.io/t/balenaengine-fails-on-raspbian/96249/25 "2020-11-24T08:28:11Z")

</div>

Hi Juan

What is the status of this?  
I am unsure how to install the latest version, like which version (arch) to use, so an updated install script would be very much appreciated!

Thanks in advance

---

<div class="post-metadata">

**Author:** ![20k-ultra](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/20k-ultra/32/3435_2.png) [@20k-ultra](https://forums.balena.io/u/20k-ultra)\
**Post date:** [November 30, 2020, 11:52pm UTC](https://forums.balena.io/t/balenaengine-fails-on-raspbian/96249/39 "2020-11-30T23:52:02Z")

</div>

We are updating the engine site and we’ll let you know shortly. If you want this now though I’d recommend you download the install script and manually edit the tag variable found on line 3 to be:

```auto
tag="v18.9.7"

```

---

<div class="post-metadata">

**Author:** ![kirchhof](https://avatars.discourse-cdn.com/v4/letter/k/ce7236/32.png) [@kirchhof](https://forums.balena.io/u/kirchhof)\
**Post date:** [December 28, 2020, 12:29am UTC](https://forums.balena.io/t/balenaengine-fails-on-raspbian/96249/42 "2020-12-28T00:29:36Z")

</div>

I tried to reproduce the problem again using the “steps to reproduce” from my original post. It seems to be working now. From my perspective, the issue is now resolved. Thank you very much for your support.