This requires: extsdk & toaster container: add --rootdir and --workdir example usage: $docker run --rm -it -v myOneVolume:/external poky/toaster --rootdir=/external --workdir=toaster-release so you could also do: $docker run --rm -it -v myOneVolume:/external poky/toaster-master --rootdir=/external --workdir=toaster-master and: $docker run --rm -it -v myOneVolume:/external poky/extsdk-container --rootdir=/external --workdir=esdk --- For advanced usage also support: $docker run --rm -it -v myOneVolume:/COW poky/toaster --rootdir='' --workdir=/COW in case they need an abs path for some reason --- for the poky container: just keep the workdir argument ad an absolute path since the poky container is not adding any files and is just using the workdir to determine the uid/gid ---- If the dir is not there, error. ----
Since 9502 was M1(Hight) and moved to M2, I don't think this should take precedence over it. This should probably be moved to M2 as well.
Moving to M3
Moving to Joshua . In case the examples (which outline the solution more than the problem) aren't clear. The goal of this enhancement is to allow more than 1 container to feed off of one docker volume. Right now, when you do a mount of a volume into the container, the extsdk and toaster containers do not have a way to work from a subdirectory of the mounted volume. This enhancement would introduce an additional command line option to separate the externally mounted volume from the working subdirectory. This is important in these cases because both the toaster and extsdk containers create files at the top of the working directory.
resetting to Joshua
Tim, Help us understand this if you have time for it.
Bulk move from 4.99 or 0.00 to 5.99
Bumping to 6.99. This depends on the fate of CROPS and whether the new container workflow enabled recently in meta-virtualization becomes the new way to support containers (including "build" containers) for the Yocto Project.