This repository has been archived by the owner on Jul 29, 2018. It is now read-only.
service-manager command kills running docker containers on first execution #12
Labels
Milestone
From @hferentschik on December 16, 2015 12:7
vagrant adbinfo
kills all running Docker containers on first execution (for example the running OpenShift container as per https://github.com/redhat-developer-tooling/openshift-vagrant setup).This is due to the fact that
adbinfo
re-generates TLS certificates for the Docker daemon when it is first called - https://github.com/projectatomic/vagrant-adbinfo/blob/master/lib/command.rb#L65. As part of this the Docker daemon gets restarted which kills all already running containers. In the context of redhat-developer-tooling/openshift-vagrant this means that after a first call tovagrant adbinfo
,vagrant provision
needs to be called again, in order to restart the OpenShift container.The plugin should not do these VM modifications steps as part of the command execution, but it should rather register itself as a provisioner and do the required changes as part of the VM bootstrap.
Copied from original issue: projectatomic/vagrant-adbinfo#55
The text was updated successfully, but these errors were encountered: