[BUG] Mark-sweep error upon initial stage

[FahdiiiG]

Environment

Self-Hosted (Docker)

Version

Latest (arm32v7 tag)

Describe the problem

Running dashy in docker on an RPi 3b+.
Getting the following error upon glancing at the logs.
IMGUR

Any ideas guys?

Running via Stack in Portainer with the following syntax:

version: '3.3'
services:
    dashy:
        container_name: dashy
        restart: always
        privileged: true
        ports:
            - '4000:80'
        volumes:
            - '/home/pi/Docker/dashy/conf.yml:/app/public/conf.yml'
        image: 'lissy93/dashy:arm32v7'

Also tried via the command
docker run -d --name dashy --restart=always --privileged -p 4000:80 -v ~/Docker/dashy/conf.yml:/app/public/conf.yml lissy93/dashy:arm32v7

Additional info

This error occurs upon initial start and keeps looping back if the container isn't stopped.

Please tick the boxes

• You are using a supported version of Dashy (check the first two digits of the version number)
• You've checked that this issue hasn't already been raised
• You've checked the docs and troubleshooting guide
• You agree to the code of conduct

[liss-bot]

Welcome to Dashy 👋
It's great to have you here, but unfortunately your ticket has been closed to prevent spam. Before reopening this issue, please ensure the following criteria are met.

Issues are sometimes closed when users:

• Have only recently joined GitHub
• Have not yet stared this repository
• Have not previously interacted with the repo

Before you reopen this issue, please also ensure that:

• You have checked that a similar issue does not already exist
• You have checked the documentation for an existing solution
• You have completed the relevant sections in the Issue template

Once you have verified the above standards are met, you may reopen this issue. Sorry for any inconvenience caused, I'm just a bot, and sometimes make mistakes 🤖

[Lissy93]

Hmm looks like not enough memory. There is a spike in memory usage when the container first starts, and the app builds for the first time, but it shouldn't be enough to prevent it running on a Pi (I've run it on a Pi 3 no problems) 🤔

[FahdiiiG]

Hmm looks like not enough memory. There is a spike in memory usage when the container first starts, and the app builds for the first time, but it shouldn't be enough to prevent it running on a Pi (I've run it on a Pi 3 no problems) 🤔

I even tried the --privileged route, just in case.

[Lissy93]

Yeah, you don't need to run with privilages, and it's best not to
I'll have another look into it, but also am working on a Lite version, whch will be much lighter-weight, and have no probelm on low-powerd SBCs. If I can't find a solution to this one, I'll update you when the lite version is out, as that will easily run on your system :)

[FahdiiiG]

Yeah, you don't need to run with privilages, and it's best not to I'll have another look into it, but also am working on a Lite version, whch will be much lighter-weight, and have no probelm on low-powerd SBCs. If I can't find a solution to this one, I'll update you when the lite version is out, as that will easily run on your system :)

Glad to hear that. I'll be waiting then. :D

For reference purposes, here are the stats after rebooting the pi (3 apps, 4 containers. Portainer, nginx proxy manager and rtorrent_rutorrent) and letting it run for a few (~10ish) minutes.
Load Average
Memory
Swap