Post by rayancaleb on Feb 15, 2018 8:07:21 GMT
Hi,
Surely, there is docker cp but this would duplicate the amount of occupied disk space. In my case, a read-only access from the host side would fully suffice, and the container itself where the data stem from is also run in read-only mode. So it would be a pity to waste the storage; besides this, some mechanism must take care of repeating the copy process every time a newer image version has been pulled (the upgrades are supposed to happen on regular base, but not on every invocation of docker run).
Another “workaround” would be to parse the output of docker inspect for mount points and issue a mount --bind command, but this also has two drawbacks.
For more details
Renewable Energy Video
Surely, there is docker cp but this would duplicate the amount of occupied disk space. In my case, a read-only access from the host side would fully suffice, and the container itself where the data stem from is also run in read-only mode. So it would be a pity to waste the storage; besides this, some mechanism must take care of repeating the copy process every time a newer image version has been pulled (the upgrades are supposed to happen on regular base, but not on every invocation of docker run).
Another “workaround” would be to parse the output of docker inspect for mount points and issue a mount --bind command, but this also has two drawbacks.
For more details
Renewable Energy Video