-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shell provisioning using docker-exec instead of SSH #8145
Comments
Hi. Thank you and have a nice day. |
Now that vagrant supports running docker directly on MacOS and Win, this would be even more useful. Ability to use any docker image without modification is a strong feature. We would be now able to use all kind of official images, that are not made for Vagrant. And with docker images, it is quite unusual to have sshd built in (...no need for that, when you can docker exec). |
Packer supports this I think. Using SSH is not a good choice as it isn't set up in most Docker images. |
This should be renamed to |
Warning "Provisioners will not be run since container doesn't support SSH." is output from two places.
|
Provisioner, such as vagrant/plugins/provisioners/shell/provisioner.rb Lines 25 to 32 in 1f565b8
Work with SSH is provided be |
Hello:
this now exists: https://github.com/ProxiBlue/vagrant-communicator-docker any SSH related commands will be handled using docker API |
As @chrisroberts suggested, I am resubmitting the feature request from #4179, since it wasn't actually addressed by #7377.
Being able to provision containers in the docker provider without an SSH daemon would greatly simplify (and speed up!) configuration, especially for multi-machine setups.
I currently have multiple
Dockerfiles
that just add sshd to public images from Docker Hub (postgresql, tomcat, nginx, etc); provisioning withexec
would allow me to eliminate all thedocker build
steps, and just use the public images directly.Ideally, the shell provisioner would prefer
exec
when using the docker provider (or at least fall back to it when ssh isn't available), but a separate provisioner with "shell-like" functionality would work to.It seems that #7377 already did the heavy lifting in enabling
docker exec
support, and allowing the shell provisioner to use it would be quite doable?Thank you.
The text was updated successfully, but these errors were encountered: