This repository contains Packer templates for creating Ubuntu Vagrant boxes.
个人定制化方案:
- 增加自动安装配置LNMP脚本
- 增加代理参数,让脚本根据参数判断更新APT时是否使用代理
- 更换清华大学镜像以提高更新速度
- 最小化安装的Packages,因为不用代理时小ISP的网络更新APT会出现
Hash Sum mismatch
错误 - 虚拟内存释放(swapoff)命令会因为MySQL服务而失败,所以清理前停止MySQL服务
- 安装中文语言包,解决SSH连接时
Per
的locale
报错问题 - 安装ZSH和oh-my-zsh并设置为默认SHELL
- 其他一些小调整
使用:
$ packer build -only=virtualbox-iso ubuntu.json
$ packer build -only=virtualbox-iso -var-file=ubuntu1510.json ubuntu.json
debconf: falling back to frontend: Readline
总是存在,不是dialog
包的问题,也不是因为vagrant.sh
修正了tty
的原因- 安装了ZSH并切换为默认SHELL,可是由于主题问题导致缺少字体而出现乱码。
- 分析是否需要预装php-memcached、Rredis-server、sqlite3、postgresql、HHVM
- 修改
minimize.sh
脚本,将不需要清理的包排除 - Vagrant使用
reload
是经常导致系统非法关机,会停留在GRUB界面30秒,考虑是不是将等待时间设置为1。 - Parallels tool问题解决一般,因为似乎如果虚拟机非法关机后,Vagrant就回到检查不到Parallels tool的状态
To build all the boxes, you will need VirtualBox, VMware Fusion/VMware Workstation and Parallels installed.
Parallels requires that the Parallels Virtualization SDK for Mac be installed as an additional preqrequisite.
We make use of JSON files containing user variables to build specific versions of Ubuntu.
You tell packer
to use a specific user variable file via the -var-file=
command line
option. This will override the default options on the core ubuntu.json
packer template,
which builds Ubuntu 14.04 by default.
For example, to build Ubuntu 15.04, use the following:
$ packer build -var-file=ubuntu1504.json ubuntu.json
If you want to make boxes for a specific desktop virtualization platform, use the -only
parameter. For example, to build Ubuntu 15.04 for VirtualBox:
$ packer build -only=virtualbox-iso -var-file=ubuntu1504.json ubuntu.json
The boxcutter templates currently support the following desktop virtualization strings:
parallels-iso
- Parallels desktop virtualization (Requires the Pro Edition - Desktop edition won't work)virtualbox-iso
- VirtualBox desktop virtualizationvmware-iso
- VMware Fusion or VMware Workstation desktop virtualization
We've also provided a wrapper script bin/box
for ease of use, so alternatively, you can use
the following to build Ubuntu 15.04 for all providers:
$ bin/box build ubuntu1504
Or if you just want to build Ubuntu 15.04 for VirtualBox:
$ bin/box build ubuntu1504 virtualbox
A GNU Make Makefile
drives a complete basebox creation pipeline with the following stages:
build
- Create basebox*.box
filesassure
- Verify that the basebox*.box
files produced function correctlydeliver
- Upload*.box
files to Artifactory, Atlas or an S3 bucket
The pipeline is driven via the following targets, making it easy for you to include them in your favourite CI tool:
make build # Build all available box types
make assure # Run tests against all the boxes
make deliver # Upload box artifacts to a repository
make clean # Clean up build detritus
The templates respect the following network proxy environment variables and forward them on to the virtual machine environment during the box creation process, should you be using a proxy:
- http_proxy
- https_proxy
- ftp_proxy
- rsync_proxy
- no_proxy
Automated tests are written in Serverspec and require
the vagrant-serverspec
plugin to be installed with:
vagrant plugin install vagrant-serverspec
The bin/box
script has subcommands for running both the automated tests
and for performing exploratory testing.
Use the bin/box test
subcommand to run the automated Serverspec tests.
For example to execute the tests for the Ubuntu 14.04 box on VirtualBox, use
the following:
bin/box test ubuntu1404 virtualbox
Similarly, to perform exploratory testing on the VirtualBox image via ssh, run the following command:
bin/box ssh ubuntu1404 virtualbox
There are several variables that can be used to override some of the default settings in the box build process. The variables can that can be currently used are:
- cm
- cm_version
- cpus
- disk_size
- memory
- update
Changing the value of the CM
variable changes the target suffixes for
the output of make list
accordingly.
Possible values for the CM variable are:
nocm
- No configuration management toolansible
- Install Ansiblechef
- Install Chefchefdk
- Install Chef Development Kitpuppet
- Install Puppetsalt
- Install Salt
You can also specify a variable CM_VERSION
, if supported by the
configuration management tool, to override the default of latest
.
The value of CM_VERSION
should have the form x.y
or x.y.z
,
such as CM_VERSION := 11.12.4
The variable HEADLESS
can be set to run Packer in headless mode.
Set HEADLESS := true
, the default is false.
The variable UPDATE
can be used to perform OS patch management. The
default is to not apply OS updates by default. When UPDATE := true
,
the latest OS updates will be applied.
The variable PACKER
can be used to set the path to the packer binary.
The default is packer
.
The variable ISO_PATH
can be used to set the path to a directory with
OS install images. This override is commonly used to speed up Packer builds
by pointing at pre-downloaded ISOs instead of using the default download
Internet URLs.
The variables SSH_USERNAME
and SSH_PASSWORD
can be used to change the
default name & password from the default vagrant
/vagrant
respectively.
The variable INSTALL_VAGRANT_KEY
can be set to turn off installation of the
default insecure vagrant key when the image is being used outside of vagrant.
Set INSTALL_VAGRANT_KEY := false
, the default is true.
- Fork and clone the repo.
- Create a new branch, please don't work in your
master
branch directly. - Add new Serverspec or Bats tests in the
test/
subtree for the change you want to make. Runmake test
on a relevant template to see the tests fail (likemake test-virtualbox/ubuntu1404
). - Fix stuff. Use
make ssh
to interactively test your box (likemake ssh-virtualbox/ubuntu1404
). - Run
make test
on a relevant template (likemake test-virtualbox/ubuntu1404
) to see if the tests pass. Repeat steps 3-5 until done. - Update
README.md
andAUTHORS
to reflect any changes. - If you have a large change in mind, it is still preferred that you split them into small commits. Good commit messages are important. The git documentatproject has some nice guidelines on writing descriptive commit messages.
- Push to your fork and submit a pull request.
- Once submitted, a full
make test
run will be performed against your change in the build farm. You will be notified if the test suite fails.
Contact [email protected]
Parallels provides a Business Edition license of their software to run on the basebox build farm.
SmartyStreets is providing basebox hosting for the box-cutter project.