有可能是流浪使用操作系统.ISO安装映像直接/或动态的ISO创建一个流浪盒子? [英] Is it possible for Vagrant to use an OS .ISO install image directly/or create a Vagrant box from an ISO on the fly?

查看:226
本文介绍了有可能是流浪使用操作系统.ISO安装映像直接/或动态的ISO创建一个流浪盒子?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

是否有可能安装自动颠沛流离.box的文件创建一个操作系统,从原来的ISO?

Is it possible to automate the creation of a Vagrant .box file for an OS install, from the original ISO?

在我看来,这是在终端到终端的自动化操作系统的显著差距上流浪提供一个虚拟机安装和配置。

To me, this is a significant gap in the end-to-end automation of Operating System install and configuration on a Virtual Machine that Vagrant provides.

当然,VagrantBox.es提供了许多基础.box的操作系统安装文件的使用。但也有一些来自第三方供应商,而不是从原来的操作系统分发机。例如Arch Linux的:Arch Linux的64(2012-07-02)<一个href=\"http://vagrant.pouss.in/archlinux_2012-07-02.box\">http://vagrant.pouss.in/archlinux_2012-07-02.box

Sure, VagrantBox.es provides many base .box OS install files for usage. But some are from third party suppliers and not from the original OS distribution maker. For example Arch Linux: Arch Linux 64 (2012-07-02) http://vagrant.pouss.in/archlinux_2012-07-02.box

不想被负有关第三方供应商的努力,但有些组织可能希望原始从原来的操作系统供应商(如上面的拱门例如安装映像,这将是:的https://www.archlinux.org/download/ )。对于希望原来安装映像的原因是安全(因为它不可能来验证安全威胁和恶意软件的第三方图像),并获取图像按预期无不需要多余的东西原来的供应商。另一个原因是采取从原来的供应商优势的新版本直接,而不必等到第三方来释放它作为一个流浪.box的

Not wanting to be negative about the efforts of third-party suppliers, but some organisations may want the original install image from the original OS provider (e.g. for the Arch example above, this would be: https://www.archlinux.org/download/ ). Reasons for wanting original install image would be security (as it would not be possible to verify the third party image for security compromises and malware) and getting the image as the original suppliers intended without extra stuff not required. Another reason would be to take advantage of new releases direct from the original supplier and not have to wait for a third party to release it as a Vagrant .box

有用于从ISO镜像创建.box的文件指南:

There are guides for creating a .box file from a .ISO image:

但这些都是手工操作 - 这违背后面的自动化和一致性的流浪汉哲学。特别是如果许多想达到能够使用原来的最终目标 - 这最终会与每个人的一部分重复劳动

But these are manual steps - which goes against the philosphy behind Vagrant of automation and consistency. Especially if many want to achieve the end goal of being able to use the original - this would end up with duplicate effort on everyone's part.

所以我会从描述了如何制作一个通用的自动化脚本转换.ISO OS安装映像到流浪盒一个明确的答案看这里。

So I would be looking here from a definitive answer that describes how to make a generic automation script to convert a .ISO OS install image into a Vagrant box.

推荐答案

我觉得VeeWee为$ P $从ISO pparing颠沛流离的盒子一个伟大的机制:

I think VeeWee provides a great mechanism for preparing a Vagrant box from an ISO:

https://github.com/jedi4ever/veewee

它已经提供了很多外的现成模板,对于大多数发行版,它可以根据需要定制(虽然这通常不需要)。另外,您可以创建自己的定义。

It already provides a lot of out-of-the-box templates for most distributions, which you can customize if required (although this is often not needed). Alternatively you can create your own definitions.

另外,您可以用打包机:

Alternatively you can use Packer:

https://packer.io/

这是由同一家公司,使无业游民,所以它具有较好的集成生产。帕克本身不提供的样本模板,​​我相信,但如果你喜欢,你可以使用那些木偶实验室用于其自己的测试目的:

Which is produced by the same company that makes Vagrant, so it has fairly good integration. Packer itself doesn't provided sample templates I believe, but you can use the ones Puppet Labs uses for its own testing purposes if you like:

<一个href=\"https://github.com/puppetlabs/puppetlabs-packer\">https://github.com/puppetlabs/puppetlabs-packer

这可以被用来作为自己的模板,一个坚实的基础,并修改品尝,也可以对项目如果需要,有助于提高回公关。

This can be used as a solid base for your own templates and modified to taste, or you can raise a PR on the project to contribute back if desired.

这篇关于有可能是流浪使用操作系统.ISO安装映像直接/或动态的ISO创建一个流浪盒子?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆