Add MKNOD capability to dockershell container

[JohnTheCoolingFan]

Description

Added arguments --cap-add MKNOD to docker run command to allow losetup -f to create the loop device node.
Fixes #6568

GitHub issue reference: #6568
Jira reference number AR-2132

How Has This Been Tested?

Running ./compile.sh build BOARD=odroidm1 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=bookworm (auto defaults to build in docker)

Checklist:

Please delete options that are not relevant.

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

[ColorfulRhino]

Thanks!

[rpardini]

Worth noting: this is adding the cap to the dockershell cli command only

[rpardini]

How Has This Been Tested?

Running ./compile.sh build BOARD=odroidm1 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=bookworm

This doesn't match the code change done. The change affects dockershell only!

[JohnTheCoolingFan]

@rpardini it auto defaults to docker on my machine, that's why.
This affects the docker script, and in my use case - that command, ran on THE HOST launches the build in docker. I don't know the option to force docker off the top of my head, so that's how I tested it. First ./compile.sh KERNEL_GIT=shallow to reproduce the issue and then copied the full command that was printed to stdout

[rpardini]

I can't follow. The PR only changes dockershell.

[JohnTheCoolingFan]

I can't follow. The PR only changes dockershell.

I finally understand what you were talking about.
I assumed that build would call womething from cli-docker.sh to relaunch in docker and build in docker, looks like that's not the case. Will do a follow-up.

It won't hurt to add that capability to dockershell as well, but I apologize for the misunderstanding on my part.

The difficulty of testing is that after a first failed run the /dev/loop0 device stays and in the next docker launch it is available and I can't find the way to remove it without rebooting the system.