Is your feature request related to a problem? Please describe.
--volumes-from
is an option provided by the docker cli commeand and it is not yet supported in Portainer.
Describe the solution you'd like
I think the best way to integrate this into the existing UI/UX of Portainer would be to add a dropdown select box to the volumes tab to select from existing containers for the --volumes-from
parameter.
Describe alternatives you've considered
To my knowledge there's no other way to use this option yet and as I learned it's considered bad UX to just enable people to send custom command line args to the process through an input field. This would probably be an alterative otherweise.
Portainer is an opinionated system, and because of this we provide a way to run Docker in a standardised and arguably, safer, way.
I personally do not believe “volumes from” has any place in an enterprise/production deployment as it encourages behaviours that do not align to docker best practices for data persistence.
My preference is not to add this feature.
Why do you need this function?
Rgds,
Neil Cresswell
On 11/09/2018, at 11:17 PM, Helmi <[email protected]notifications@github.com> wrote:
Is your feature request related to a problem? Please describe.
--volumes-from is an option provided by the docker cli commeand and it is not yet supported in Portainer.
Describe the solution you'd like
I think the best way to integrate this into the existing UI/UX of Portainer would be to add a dropdown select box to the volumes tab to select from existing containers for the --volumes-from parameter.
Describe alternatives you've considered
To my knowledge there's no other way to use this option yet and as I learned it's considered bad UX to just enable people to send custom command line args to the process through an input field. This would probably be an alterative otherweise.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_portainer_portainer_issues_2267&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=MW-u4k-8D4WtVfRv52NhFYYYgVTLQccjiIHWcx0AhgA&s=vlnKTOo9_jskSi-NNJMkcob8MNEDEyCOJES5fdHVk1c&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AWGrlQxYdb-5FEHi3onxylr9DHY0dQQjsQks5uZ5vAgaJpZM4WjGcB&d=DwMCaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=MW-u4k-8D4WtVfRv52NhFYYYgVTLQccjiIHWcx0AhgA&s=ATsibTqgbClX95iHDFBKe3_xnRAmTJBeyoFqlK11XGg&e=.
As this issue is still open...
We use the volumes-from for running backups, either full database backups or cloud backups using something like Duplicati or other S3 compatible storage.
Since Portainer does not support this we currently work around this limitation by using bind mounts or add backup software to the container that needs backups running...
I'm also looking for this.
Most helpful comment
As this issue is still open...
We use the volumes-from for running backups, either full database backups or cloud backups using something like Duplicati or other S3 compatible storage.
Since Portainer does not support this we currently work around this limitation by using bind mounts or add backup software to the container that needs backups running...