| Summary: | support the multiple containers working off 1 volume model | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] CROPS | Reporter: | brian avery <brian.avery> |
| Component: | crops-default | Assignee: | Unassigned <unassigned> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | randy.macleod, tim.orling |
| Version: | 2.3 | ||
| Target Milestone: | 6.99 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
brian avery
2016-10-18 20:33:33 UTC
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. |