QB does not mount any default paths like "/etc/ssl/certs". For absolute path mounting, I filed an improvement request:

Please watch to get notified when fixed (will be addressed in next patch release)

Thanks Robin!

One more question regarding the docker step.
There is an "Interpreter" option which then generates a --entrypoint parameter in the docker command, however I would like to leave this empty and not set this parameter.
Currently that is not possible. Could this be changed or is there a reason why this is a mandatory option?

The shell/batch command needs this setting to interprete commands. If you just need to invoke docker container with its entrypoint, maybe the run docker container step is what you need?

This --entrypoint parameter causes a skip of the user creation of the docker image. Therefore I'm root inside the container which causes me a problem.
I can't use --user parameter in "options" field of quickbuild because the user that I want doesn't exist because of the before mentioned skip.

Maybe using this "docker shell" step is wrong.
My goal of that step is to:

• Run docker image
• Run a build inside image (as normal user)
• Done

Currently I'm using normal shell step and do the docker commands from there.
Using only the "run docker container" step might also be an option but with the "docker shell" step I can't find a solution at the moment.

How do you use this image without QB? Is entrypoint of the image starts a shell so that you can run specified commands inside it?

Yes, wihtout QB I use "docker run" command, that starts me a shell where I then run build commands.

In QB I use now step of type "Shell/Batch Command".
Then run "docker run" command and pass the docker run command a script to run inside image.

Run docker command:

docker run --rm -it \
  -v "${PWD}":/home/"${docker_user}"/"${docker_workdir}" \
  -v "${HOME}"/.gitconfig:/home/"${docker_user}"/.gitconfig:ro \
  -v /tmp/.X11-unix:/tmp/.X11-unix \
  -v "${HOME}"/.Xauthority:/home/"${docker_user}"/.Xauthority:rw \
  -v /etc/ssl/certs/:/etc/ssl/certs/:ro \
  --workdir=/home/"${docker_user}"/"${docker_workdir}" \
  secodocker/clea-os-builder:22.04 --username="${docker_user}"

Build command inside docker image:

. ./seco-setup.sh -d seco_intel_clea-os_embedded
. ./seco-setup.sh -c
bitbake seco-clea-os-image

In one of my team's projects, they are able to accomplish this by passing additional "-v" parameters in the "Options" field of the step. I don't like this solution; it makes the code less readable, but it does allow more flexibility since they can use a variable to have different mounts for different child configurations AND declare mounts to be read-only:

Options: [ --hostname ${vars.getVariable("friendlyName")} ${vars.getValue("customMountParams")} ]
Variable customMountParams = [ -e MAVEN_ARGS="-gs /tmp/settings/.m2/settings.xml" -v /home/build/.m2:/tmp/settings/.m2:ro" ]

My preferred solution is to copy the relevant files into the configuration workspace so that everything required is in one place.

You may use "run container step" in this case:

1. Put your build commands into a shell script
2. Mount the directory containing the shell script into container
3. Specify path to build script inside container as container argument

PS: QB 15.0.31 supports to mount absolute path into container now

Great, thanks for the quick replies and support of absolute paths.
I'll try this to see what suits us best.