You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 31, 2019. It is now read-only.
Instead of copying files at the build, you can mount it at the run with -v option. (-v /home/CNSMO/ENVS/VPNClient-slave.1/client.conf:/etc/openvpn/client.conf:ro)
Multiple files can be mounted.
If files are mounted, you could publish the container on a public repo and get it instead of compiling it.
Doing this can speed up the deployment significantly (compiling the docker can be very slow).
The text was updated successfully, but these errors were encountered:
isartcanyameres
changed the title
Speed up deployment by mounting files at run instead of copying them
Speed up deployment by mounting files at run instead of copying them at build
Jul 21, 2016
Instead of copying files at the build, you can mount it at the run with -v
option. (-v
/home/CNSMO/ENVS/VPNClient-slave.1/client.conf:/etc/openvpn/client.conf:ro)
Multiple files can be mounted.
If files are mounted, you could publish the container on a public repo and
get it instead of compiling it.
Doing this can speed up the deployment significantly (compiling the docker
can be very slow).
The information contained in this electronic mail message is confidential.
It is intended solely for the use of the individual or entity to whom it is
addressed and others authorised to receive it. If the reader of this
message is not the intended recipient, you are hereby notified that any
use, copying, dissemination or disclosure of this information is strictly
prohibited. If you receive this e-mail message in error please notify me
Instead of copying files at the build, you can mount it at the run with -v option. (-v /home/CNSMO/ENVS/VPNClient-slave.1/client.conf:/etc/openvpn/client.conf:ro)
Multiple files can be mounted.
If files are mounted, you could publish the container on a public repo and get it instead of compiling it.
Doing this can speed up the deployment significantly (compiling the docker can be very slow).
The text was updated successfully, but these errors were encountered: