to support the multiple volume approach we should extend the samba contianer to take a list of volumes/dirs and export all of them. We should hold off documenting this except for the docker run --help part until we do an "advanced user" section.
Moving to Joshua. The samba container is needed in order to provide a view of the filesystem from a windows/mac host. Currently the assumption is that you have one docker volume and one samba container. It would be nice to enable multiple volumes (say pyro, rocko,...) all being served by 1 samba container. The samba container is unique due to needing to have a port available. This can be trivially worked around by just using multiple directories on 1 volume.
(In reply to brian avery from comment #0) > to support the multiple volume approach we should extend the samba contianer > to take a list of volumes/dirs and export all of them. > > We should hold off documenting this except for the docker run --help part > until we do an "advanced user" section. s
Ideas here are probably still valid for future design considerations.