Documentation improvements needed

[pietrushnic]

For example, I get information about building some meta layer e.g. meta-virtualization, that information requires me to correctly modify bblayers.conf but because I'm not sure how everything is mounted inside the container I'm not sure how to modify paths to layers.

Second thing is that build directory appears after sourcing oe-init-build-env what means after the first call of yocto-docker container, before that call, there is no infrastructure to modify build/conf files. Any idea what we can do about that? It confused me when getting back to that project after some time.

[macpijan]

@pietrushnic
Ad.1 Originally we mounted $PWD:$PWD in order to preserve paths from the host so you would not need to wonder and just provide the host paths: https://github.com/3mdeb/yocto-docker/blob/master/docker-bake.sh#L52

Ad.2 Yes, that is how the YP works. Maybe link to documentation: https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#structure-core-script

[pietrushnic]

@macpijan I think that behavior may surprise new users, we should make sure that trying this project is seamless. Having above assumptions can scare some users - most people will not take time to figure out what is going on. IMO we should have most simple real life scenario from scratch in README. What you think?

[macpijan]

@TomaszAIR Please take a look at it. I'm not sure if we still e this container and if this issue is still valid.