User reports RPi4 2GB has it's UI service on a restart loop

[jellyfish-bot]

[thgreasi] That's on a fresh DWB installation w/ balenaOS 2.56.0. The boinc-client was running properly but the UI was in a restart loop.
Supervisor logs:

[debug]   Replacing container for service ui because of config changes:
[debug]     Non-array fields:  {"added":{},"deleted":{},"updated":{"memReservation":16777216}}
[debug]   Replacing container for service ui because of config changes:
[debug]     Non-array fields:  {"added":{},"deleted":{},"updated":{"memReservation":16777216}}
[warn]    Ignoring unsupported or unknown compose fields: blkioConfig
[event]   Event: Service install {"service":{"appId":1753819,"serviceId":728349,"serviceName":"ui","releaseId":1560674}}
[event]   Event: Service installed {"service":{"appId":1753819,"serviceId":728349,"serviceName":"ui","releaseId":1560674}}
[event]   Event: Service start {"service":{"appId":1753819,"serviceId":728349,"serviceName":"ui","releaseId":1560674}}
[event]   Event: Service started {"service":{"appId":1753819,"serviceId":728349,"serviceName":"ui","releaseId":1560674}}
[warn]    Ignoring unsupported or unknown compose fields: blkioConfig

This also kept happening even after stopping the bloinc-client and having some RAM being freed.

[jellyfish-bot]

[thgreasi] This issue has attached support thread https://jel.ly.fish/8a158c75-4185-4bee-bad3-1eac8ca5201f

[dtischler]

Duplicated this issue on a 2gb unit here, as well. Boinc Client did grab a work unit, and is crunching protein. But 'ui' container is looping for me as well.

[Kore-Development]

Same issue for me

[GOTO-GOSUB]

I have a similar issue an a 4GB Pi 4 but it has manifested in a different way. I have detailed this in greater depth here: https://forums.balena.io/t/fold-on-pi-4-keeps-restarting-the-ui/216098

The terminal keeps going through this cycle, over and over:

25.11.20 09:43:35 (+0000)
25.11.20 09:43:35 (+0000) > [email protected] start /usr/app/dashboard
25.11.20 09:43:35 (+0000) > node server.js
25.11.20 09:43:35 (+0000)
25.11.20 09:43:37 (+0000) Service exited ‘ui sha256:490(redacted, always the same)174d8’
25.11.20 09:43:37 (+0000) Killed service ‘ui sha256:490(redacted, always the same)174d8’
25.11.20 09:43:38 (+0000) Installing service ‘ui sha256:490(redacted, always the same)174d8’
25.11.20 09:43:39 (+0000) Installed service ‘ui sha256:490(redacted, always the same)174d8’
25.11.20 09:43:39 (+0000) Starting service ‘ui sha256:490(redacted, always the same)174d8’
25.11.20 09:43:42 (+0000) Started service ‘ui sha256:490(redacted, always the same)174d8’
25.11.20 09:43:42 (+0000) 2020/11/25 09:43:42 Permitting clients to write input to the PTY.
25.11.20 09:43:42 (+0000) 2020/11/25 09:43:42 Server is starting with command: boinctui
25.11.20 09:43:42 (+0000) 2020/11/25 09:43:42 URL: http://127.0.0.1:8080/
25.11.20 09:43:42 (+0000) 2020/11/25 09:43:42 URL: (redacted)/
25.11.20 09:43:42 (+0000) 2020/11/25 09:43:42 URL: (redacted)/
25.11.20 09:43:43 (+0000) Killing service ‘ui sha256:490(redacted, always the same)174d8’
25.11.20 09:43:44 (+0000)
25.11.20 09:43:44 (+0000) > [email protected] start /usr/app/dashboard
25.11.20 09:43:44 (+0000) > node server.js
25.11.20 09:43:44 (+0000)

The number crunching appears to be working in all other respects.

[jellyfish-bot]

[gelbal] This issue has attached support thread https://jel.ly.fish/2890ed0a-d515-4a58-b1f0-a0eb17b115f4

[pdcastro]

I gather that @pipex was able to reproduce this issue (internal JF thread), and he found that a workaround is to add cgroup_enable=memory to the cmdline.txt file. This text file can be found in the resin-boot partition of the SD card after it is flashed. Take the SD card out of the Pi, connect the SD card to a laptop / desktop computer, and edit the cmdline.txt file in the resin-boot partition. (This is easy on macOS, as Finder automatically mounts the resin-boot partition. On Linux and Windows, additional steps are required.) Then insert the SD card to the Pi 4 again.

This issue looks similar to moby/moby#35587 (also found by @pipex).