简体   繁体   English

我需要在我无业游民的盒子上放露比和厨师吗

[英]Do I Need Ruby and Chef On My Vagrant Box

I am using the trusty64 vagrant box and I provision it using puppet. 我正在使用trusty64 vagrant框,并使用p配置它。

I just noticed today that ruby and chef are installed and I don't use either of them for my VM work. 我今天才注意到,已经安装了ruby和Chef,并且在我的VM工作中没有使用它们中的任何一个。

Do I need them there for Vagrant to do its magic? 我需要他们在那里让流浪汉做魔术吗?

Can I remove them after my VM is provisioned or will vagrant halt and vagrant up stop working? 我可以在调配虚拟机后将其删除,还是vagrant up停止工作并vagrant halt vagrant up工作?

so to the question 所以这个问题

Do I Need Ruby and Chef On My Vagrant Box 我需要在我无业游民的盒子上放露比和厨师吗

Its mainly up to you. 它主要取决于您。

no, more seriously: 不,更严重的是:

  • Ruby comes install with Linux distro, generally some older version but its a fact that it is delivered (as python, perl ...) so you should leave it. Ruby随Linux发行版一起安装,通常是一些较旧的版本,但实际上它已交付(如python,perl ...),因此您应该保留它。 It is not doing any harm and some other tools (including chef and puppet) relies on Ruby to be installed so if you provision with puppet you must leave ruby 它没有任何危害,并且某些其他工具(包括Chef和Puppet)依赖于Ruby进行安装,因此,如果您配置Puppet,则必须保留ruby

Vagrant does not rely on ruby to be installed on the guest to do its magic, its mainly issuing ssh script command to do the update on network/hostname ... Vagrant不依赖于在客户机上安装ruby来做魔术,它主要发布ssh脚本命令来对网络/主机名进行更新...

  • trustry64 box is an official box from hashicorp (the company behind vagrant) and vagrant does support out of the box chef and puppet provisioning those tools are installed. trustry64 box是hashicorp(vagrant背后的公司)的官方包装,vagrant确实支持厨师和木偶,只要安装了这些工具即可。 Again they don't make any harm even if you're not using it. 同样,即使您不使用它们,它们也不会造成任何伤害。

The thing is that your box will have ruby and chef installed and whenever you boot a new VM from this box, it will contain ruby and chef, I think you will spend more time cleaning the booted VM at the end of the day, specially if you have to destroy/rebuild the VM. 问题是您的盒子将安装ruby and cook,并且每当您从盒子中启动新VM时,其中都会包含ruby和cook,我想您会在一天结束时花更多时间清洁启动的VM,特别是如果您必须销毁/重建虚拟机。

If you want a minimalist box that contains only the thing you need, you can look at packer - packer is a tool to automate the creation of vagrant box, so you can really control what is install from the iso file of the OS to the libraries and 3rd party tools. 如果您想要一个仅包含所需物品的简约包装盒,则可以查看packer -packer是一种用于自动创建无用物品包装盒的工具,因此您可以真正控制从OS的iso文件到库的安装内容和第三方工具。

Vagrant does rely on ruby installed in the box if you are using chef or puppet provisioner. 如果您使用的是厨师或木偶供应商,那么Vagrant确实依赖于安装在盒子中的红宝石。 chef/puppet runs happen inside the guest box which vagrant orchestrates using ssh. 厨师/人偶的运行发生在来宾流氓使用ssh进行协调的来宾框内。

You can remove chef when you will use chef provisioner,vagrant will download and install it again but you would need ruby for puppet. 您可以在使用厨师调配器时删除厨师,流浪者会再次下载并安装它,但是您需要使用红宝石作为木偶。 See puppet install dependency here 在此处查看puppet安装依赖项

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 如何确定Vagrant盒子中最初安装了Chef的位置? - How do I determine where chef is initially installed in my Vagrant box? 如何在厨师的流浪汉盒子上安装PECL软件包? - How do I install a PECL package on Vagrant box with chef? 如何使用Chef在无业游民的centos盒子上设置omnibus builder环境? - How do I set up omnibus builder environment on vagrant centos box using chef? 如何配置Chef Solo以在新的Vagrant盒子上安装Nginx? - How do I configure Chef Solo to install Nginx on a new Vagrant box? 为什么每次将sag sva放入我的游民箱时都必须运行捆绑安装 - Why do I have to run bundle install every time I vagrant ssh into my vagrant box 使用 Chef-solo 和 vagrant 配置 Vagrant box - Provisioning Vagrant box with chef-solo and vagrant Vagrant RDP => Windows2012R2 | 我如何 rdp 进入我的流浪盒子? - Vagrant RDP => Windows2012R2 | How do I rdp into my vagrant box? 使用从GitHub克隆的Vagrant + Chef + Wordpress(VCCW)存储库时,我在哪里放置自己的代码? - Where do I place my own code whilst using Vagrant+Chef+Wordpress (VCCW) repository cloned from GitHub? 使用无业游民的盒子时,我需要为livereload添加转发端口吗? - Do I need to add a forwarded port for livereload when using a vagrant box? 配备Chef_Solo的调配无家可归者盒子 - Provisioning vagrant box with chef_ solo
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM