Hi,
I’m starting in the world of Balena OS and try to build this repository :
I set the first condition that have an OS that boot with cgroup v1 enable.
See the log :
> stat -fc %T /sys/fs/cgroup
tmpfs
I double check by running this command in an Alpine container :
> docker run --rm alpine stat -fc %T /sys/fs/cgroup
tmpfs
And I third check by checking the Docker configuration :
> docker info | grep -i cgroup
WARNING: Running in rootless-mode without cgroups. To enable cgroups in rootless-mode, you need to boot the system in cgroup v2 mode.
WARNING: Support for cgroup v1 is deprecated and planned to be removed by no later than May 2029 (
)
Cgroup Driver: none
Cgroup Version: 1
In the README, they don’t ask to launch Docker in root mode so I run it rootless :
> ./balena-yocto-scripts/build/balena-build.sh -d imx8mm-lpddr4-evk -s /home/maxime/balena/balena-fsl-arm/build
I get this error :
> ./balena-yocto-scripts/build/balena-build.sh -d imx8mm-lpddr4-evk -s /home/maxime/balena/balena-fsl-arm/build
[balena_lib_environment]: Defaulting to balena-cloud.com
[balena_lib_environment]: Defaulting to balena-cloud.com
~/balena/balena-fsl-arm ~/balena/balena-fsl-arm
Submodule details:
Submodule details: /home/maxime/balena/balena-fsl-arm
9f18bf21add2a8a3ffa0b96aba7416ba2d752e27 balena-yocto-scripts (v1.39.12)
fc76558c384c10bf228b10909eca346ee9d6b564 contracts (v2.0.137)
5fdbeb1984d50a9f7c9a5e5404771838c2670d67 layers/meta-balena (v6.10.17)
0c405be0b905b239b96dc6f65a2eebc27a7e21c7 layers/meta-boundary (remotes/origin/kirkstone)
175bc45b40ea2da00baefb5b532176694d70596d layers/meta-cyclonedx (remotes/origin/kirkstone)
7286bef07802fc493894c5917a315d53c8fe2191 layers/meta-freescale (2.1-3999-g7286bef0)
9e94b64bdfebcf7bfdf2af6447cec866a4efa814 layers/meta-freescale-3rdparty (2.2-540-g9e94b64)
7d4507f226bd2af939d4482fb14a809867ece939 layers/meta-openembedded (remotes/origin/kirkstone-next-599-g7d4507f226)
ab676955a0909ed436c22c7a7e73605de1dc364a layers/meta-solidrun-arm-imx6 (remotes/origin/kirkstone)
fab6dc2fbc5229f04ae8bd34a35c301dd697c993 layers/meta-solidrun-solidsense (heads/main)
c942cdb0572ab065a13424aa7482404269ff9554 layers/poky (yocto-4.0.32-14-gc942cdb057)
~/balena/balena-fsl-arm
1.39.12-yocto-build-env: Pulling from balena-os/balena-yocto-scripts
Digest: sha256:4e21054eb70015b0593821a2b99de5f840be1194f7e812d2f46722a199b5d213
Status: Downloaded newer image for
[INFO] Creating and setting builder user 1000:1000.
unix:///var/run/docker.sock /var/run/docker.pid
[INFO] The configured git credentials for user builder are:
Resin Builder
[INFO] Running build as builder user…
Building JSON manifest…
npm ERR! code EACCES
npm ERR! syscall open
npm ERR! path /work/balena-yocto-scripts/build/package-lock.json
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, open ‘/work/balena-yocto-scripts/build/package-lock.json’
npm ERR! [Error: EACCES: permission denied, open ‘/work/balena-yocto-scripts/build/package-lock.json’] {
npm ERR! errno: -13,
npm ERR! code: ‘EACCES’,
npm ERR! syscall: ‘open’,
npm ERR! path: ‘/work/balena-yocto-scripts/build/package-lock.json’
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/builder/.npm/_logs/2026-01-28T12_10_47_344Z-debug-0.log
/work/balena-yocto-scripts/build/build-device-type-json.sh: ERROR - Please make sure the ‘npm’ package is installed and working before running this script.
[000000000][ERROR]Could not generate .json file(s).
Untagged:
Deleted: sha256:4e21054eb70015b0593821a2b99de5f840be1194f7e812d2f46722a199b5d213
I read the script that find this /work folder and it’s our current working directory. So “work/balena-yocto-scripts/build/package-lock.json” is technically “./balena-yocto-scripts/build/package-lock.json”.
The folder is own by me but the file doesn’t exist.
Am I doing something wrong ?
Context, my config :
> uname -a
Linux maxime-NucBox-K10 6.14.0-37-generic #37~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 20 10:25:38 UTC 2 x86_64 x86_64 x86_64 GNU/Linux