Container failed to start

Product support balenaOS
,
1

Hello everyone,

I am just testing BalenaOS v2.113.33 and found an error when trying to run a container:

51f6fa66aebb[1377]: [error]   Updating failed, but there's another update scheduled immediately:  Error: Failed to apply state transition steps. (HTTP code 500) server error - AppArmor e 
balena-supervisor[2024]: [error]   Updating failed, but there's another update scheduled immediately:  Error: Failed to apply state transition steps. (HTTP code 500) server error - AppAr:
51f6fa66aebb[1377]: [error]     error: exec: "apparmor_parser": executable file not found in $PATH  Steps:["start"]

This didn’t happened in previous image versions like v2.113.24. Any idea on what could be happening?

I am attaching a journalctl -xf & output plus device diagnostics json.

owa5x_balenaos_v2.113.33.log (126.7 KB)
bff7536fb6e915cbe486446921521090_checks_2023.04.11_10.38.47+0000.txt (783 Bytes)

Thanks in advance

2

Hey @floion could you please take a look at this?

Thanks!

3

Hi, have a look at linux-boundary: Ensure apparmor is disabled by acostach · Pull Request #374 · balena-os/balena-fsl-arm · GitHub

4

Thanks @floion, I am adding that to our kernel.bbappend recipe to check if that solves it, but I don’t really think that will fix it. As I see disabling AppArmor was added on version v.2.109.0 and we have successfully tested containers on v.2.113.24 so…

Any other idea?

Thanks!

5

Can be marked as closed as per linux-owasys-owa5x: ensure apparmor is disabled by owzagj · Pull Request #85 · balena-os/balena-owa5x · GitHub

1 Like