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
Unable to install another plugin into Docker based Installation #1198
Comments
It seems I've made a rather large assumption with the docker image as to how it works for subsequent plugin installs. I thought subsequent plugins were cumulative, however instead it appears to attempt to reinstall the entire set of plugins and their dependencies every time a plugin is installed. This doesn't seem like the most efficient approach, so I'll probably want switch to publishing the full version as the default, as well as a slim version with an explanation of how to add plugins to the slim version and trim down again. |
Switch to publishing the image containing all of the libraries and build dependencies needed to support the plugin being reinstalled as that is the default behaviour when vagrant installs a new plugin. This should allow the default image to be extended with additional plugins and if needed, the authors of the new image may follow and use the slim version as a base to provide a reduced size docker image. Fixes: #1198
Switch to publishing the image containing all of the libraries and build dependencies needed to support the plugin being reinstalled as that is the default behaviour when vagrant installs a new plugin. This should allow the default image to be extended with additional plugins and if needed, the authors of the new image may follow and use the slim version as a base to provide a reduced size docker image. Fixes: #1198
Steps to reproduce
vagrant plugin install --local vagrant-mutate
ERROR: Failed to build gem native extension.
Expected behaviour
Actual behaviour
Suggested solution
2 images will be built:
The CI builds the developer image first, the small image is built from the developer image. Using the developer image, local plugins can be installed. Notice: there is a bug in the vagrant (?): the local images aren't listed by below command, but the
vagrant up
can use:Used alias:
System configuration
OS/Distro version:: Lubuntu 20.04
Libvirt version: 0.3.0
Output of
vagrant version; vagrant plugin list
:Attach Output of
VAGRANT_LOG=debug vagrant ... --provider=libvirt >vagrant.log 2>&1
Not relevant.
A Vagrantfile to reproduce the issue:
Any
Are you using upstream vagrant package or your distros package?
Upstream
The text was updated successfully, but these errors were encountered: