minikube/deploy/iso/boot2docker
Praveen Kumar 60d391871b Update dockerfile to accommodate latest b2d changes.
2d5e77def8 recently merged and it will break current b2d iso creation.
2016-12-12 14:40:35 +05:30
..
Dockerfile Update dockerfile to accommodate latest b2d changes. 2016-12-12 14:40:35 +05:30
Dockerfile.conntrack boot2docker: move build files into separate directory 2016-10-13 20:02:42 +02:00
Dockerfile.ethtool boot2docker: move build files into separate directory 2016-10-13 20:02:42 +02:00
Dockerfile.socat boot2docker: move build files into separate directory 2016-10-13 20:02:42 +02:00
README.md boot2docker: move build files into separate directory 2016-10-13 20:02:42 +02:00
bootlocal.sh boot2docker: move build files into separate directory 2016-10-13 20:02:42 +02:00
build.sh boot2docker: move build files into separate directory 2016-10-13 20:02:42 +02:00
conntrack.sh boot2docker: move build files into separate directory 2016-10-13 20:02:42 +02:00

README.md

Scripts for building a VM iso based on boot2docker

Build instructions

./build.sh

Test instructions

To manually try out the built iso, you can run the following commands to create a VM:

VBoxManage createvm --name testminikube --ostype "Linux_64" --register
VBoxManage storagectl testminikube --name "IDE Controller" --add ide
VBoxManage storageattach testminikube --storagectl "IDE Controller" --port 0 --device 0 --type dvddrive --medium ./minikube.iso
VBoxManage modifyvm testminikube --memory 1024 --vrde on --vrdeaddress 127.0.0.1 --vrdeport 3390 --vrdeauthtype null

Then use the VirtualBox gui to start and open a session.

Release instructions

  • Build an iso following the above build instructions.
  • Test the iso with --iso-url=file:///$PATHTOISO.
  • Push the new iso to GCS, with a new name (minikube-0x.iso) with a command like this: gsutil cp $PATHTOISO gs://$BUCKET
  • Update the default URL in start.go.