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
Currently provisioning in vagrant takes a very long time. If an error accurs during provisioning, it requires destroy vagrant vm, fix error and make provisioning from the beginning and wait for new error or sucesss for a long time again.
If all provisioning steps would be implemented in Dockerfile by separate RUN commands, it will allow to continue building from the place where the the error occurs and not from the beginning.
Of course it's possible to use vagrant ssh and continue manualy run provisioning by provision.sh. But with docker it would be much more comfortable.
Also deploying with docker is easier and it has better perfomance than Vagrant in most cases.
The text was updated successfully, but these errors were encountered:
Docker for maposmatic.
Currently provisioning in vagrant takes a very long time. If an error accurs during provisioning, it requires destroy vagrant vm, fix error and make provisioning from the beginning and wait for new error or sucesss for a long time again.
If all provisioning steps would be implemented in Dockerfile by separate
RUN
commands, it will allow to continue building from the place where the the error occurs and not from the beginning.Of course it's possible to use
vagrant ssh
and continue manualy run provisioning byprovision.sh
. But with docker it would be much more comfortable.Also deploying with docker is easier and it has better perfomance than Vagrant in most cases.
The text was updated successfully, but these errors were encountered: