With commit minishift/minishift@868b675 , all content will be under a subdirectory.

Update Makefie post 1.7.0 release of minishift.

Good that we have a CI job now, but people also need to be able to get to it. Can we at a build status icon or if that is not enabled in our environment at least a couple of sentences of where the CI jobs are, where they are configured, link to minishift-ci-jobs repo, ...

Internally we might want to add something to the Mojo (how to log in to the Job, anything one needs to know about JBB, ...)

Currently we are using 1.12.3 docker version and even our minishift-centos iso have 1.12.6 . It good have both sync.

To provide a place for people to store optional applications/binaries that survive restarts

mkdir -p /mnt/sda1/opt
rm -rf /opt
ln -s /mnt/sda1/opt /opt
chmod o+rwx /opt

We should not always have to rebuild these images. We can push the intermediate images to Docker hub, unless specified we want to rebuild them.

This is, in my opinion, better for QA... and certainly, speeds up the build of the ISO

Updated

The issue is with how the B2D image handles the hyper-v data exchange module, which is part of the kernel. Since b2d uses a module, the values are not available in time to provide an IP address before DHCP has assigned one. The module seems to read the pool and clears the values? At least, while the WMI call as used in gbraad/go-hvkvp is received and confirmed, the value is not available, even after the module is loaded. It is therefore needed to resend the message several times... and there is no indication if the call actually succeeds.

Todo

• create minishift-staticip.sh script
  • if IpAddress is available
  • else leave DHCP setting
  • use given netmask
  • use given nameserver
  • use given gateway
• add executable to ISO image
  • first use: https://github.com/gbraad/go-hvkvp/releases/tag/0.1
  • use latest from gbraad-fedora/go-hvkvp#3

Refer: minishift/minishift#1316

Create release job similar to minishift release job to easily perform the release.

Currently, it is done from dev's machine where we are Getting bash related errors during 'make release'. in Fedora workstation.
This forced us to look for CentOS based machine.

This release job will ease all this process.

Hi all, I'm trying to create the iso from scratch with some images i need but I'm facing a problem.

When parsing the Dockerfile, I get the following error

Step 4/17 : RUN sed -i '/^b2dVersion/,/^EOOS/d' /tmp/make_iso.sh
---> Running in 08136a0424be

sed: can't read /tmp/make_iso.sh: No such file or directory
The command '/bin/sh -c sed -i '/^b2dVersion/,/^EOOS/d' /tmp/make_iso.sh' returned a non-zero code: 2
make: *** [iso] Errore 2

Anybody has a clue?

Similar to minishift-centos-iso, there should be smoke tests against minishift (preferably always the latest release).

Looks like there is change of text in minishift delete src:

$ minishift delete
Currently no Minishift VM defined.

Previously it was "Does Not Exist".

See minishift/minishift-centos-iso#21

Fixed with #52

The ISO name should be minishift-b2d.iso as per the repository name. currently it generates minishift.iso

$ bash build.sh

**************
+ xz -9 --format=lzma --verbose --verbose
+ cpio -o -H newc
xz: Filter chain: --lzma1=dict=64MiB,lc=3,lp=0,pb=2,mode=normal,nice=64,mf=bt4,depth=0
xz: 674 MiB of memory is required. The limiter is disabled.
xz: Decompression will need 65 MiB of memory.
335112 blocks
(stdin): 31.5 MiB / 163.6 MiB = 0.193, 1.5 MiB/s, 1:49
/
xorriso 1.3.2 : RockRidge filesystem manipulator, libburnia project.

Drive current: -outdev 'stdio:/boot2docker.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data,  179g free
xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rules
Added to ISO image: directory '/'='/tmp/iso'
xorriso : UPDATE : 12 files added in 1 seconds
xorriso : UPDATE : 12 files added in 1 seconds
xorriso : NOTE : Copying to System Area: 432 bytes from file '/usr/lib/ISOLINUX/isohdpfx.bin'
libisofs: NOTE : Aligned image size to cylinder size by 299 blocks
xorriso : UPDATE :  88.89% done
ISO image produced: 18432 sectors
Written to medium : 18432 sectors at LBA 0
Writing to 'stdio:/boot2docker.iso' completed successfully.

 ---> 17c1e3c89489
Removing intermediate container 6f5da9fa41c1
Step 14 : CMD cat boot2docker.iso
 ---> Running in c10ae0053861
 ---> d1c1177e2334
Removing intermediate container c10ae0053861
Successfully built d1c1177e2334
~/code/gocode/src/github.com/minishift/minishift-b2d-iso/iso
Iso available at ./minishift.iso

Currently, smoke tests only run in Linux platform. Update the tests so that it can be in Mac OS or Windows.

Current release target only works on Linux. Either get gh-release installed independent of the OS (go get!?) or make it a prerequisite to install it. As it stands now it won't work.

It would be good to show the build status of centos ci in README

Update the used Docker version to 1.12.3. See also minishift/minishift#230

If Avocado released a new version of their packages, we are able to remove the workaround to install python-setuptools from the centos_ci setup script.

Reference: avocado-framework/avocado#1798

See:

• Bug on minishift: minishift/minishift#1022
• Bug on B2D: boot2docker/boot2docker#1245

As a reference, vanilla TCL boots fine and the first broken B2D commit is the following:
boot2docker/boot2docker@7d3984d

Release version and build ID should be part of the ISO i.e. Similar to https://github.com/minishift/minishift-centos-iso/blob/master/Makefile#L36-L37

Upstream boot2docker has changed the path of make_iso.sh [1] , hence our builds will fail once we move to any docker version later v1.12.4-rc1.

We have two ways to fix this. Either [2] [3] can be fixed or we can put the make_iso.sh in our repository. We can also also fetch it from the upstream repository through the Makefile automatically every time we do a build.

[1] boot2docker/boot2docker@2d5e77d
[2] https://github.com/minishift/minishift-b2d-iso/blob/master/iso/Dockerfile#L52
[3] https://github.com/minishift/minishift-b2d-iso/blob/master/iso/Dockerfile#L25

With latest upgrades in docker, it seems that docker installation is failing in CentOs machine.
This build is failing due to that - https://ci.centos.org/job/minishift-pr/503/console.

Even getting failure error in my CentOS workstation:

[budhram@localhost ~]$ sudo yum -y install docker-engine
Loaded plugins: fastestmirror, langpacks

File contains parsing errors: file:///etc/yum.repos.d/docker.repo
	[line  2]:   name=Docker Repository

	[line  3]:   baseurl=https://yum.dockerproject.org/repo/main/centos/7/

	[line  4]:   enabled=1

	[line  5]:   gpgcheck=1

	[line  6]:   gpgkey=https://yum.dockerproject.org/gpg

Just like cifs, and ssh-fs, it is better to include nfs-utils into the image

Related to: minishift/minishift-centos-iso#118

With latest 1.6.0, we have added confirmation on delete operation. Update test accordingly.

Currently, the tests are only able to run in Linux as we are downloading only linux binary here

Currently we only have persistent storage for docker configurations but we also required for openshift. we need to do perform some mount magic which we did for our centos iso to make sure it work - https://github.com/minishift/minishift-centos-iso/blob/master/scripts/handle-user-data#L38-L42

To allow mounting of fileshares, as described in minishift/minishift#316, we need to add cifs-utils to the image.

Trying to be consistent here with minishift-centos-iso tests and also reporting structure is more natural and understanding in shell-based tests.

Currently, test case to check NFS installation has been commented out due to issue minishift/minishift#660 which is fixed now.

See https://github.com/minishift/minishift-b2d-iso/blob/master/tests/test.py#L69-L74

Also, found that mount.nfs -V <anypath> does return version. Might be bug in mount.nfs

docker@minishift:~$ sudo /sbin/mount.nfs -V 
usage: mount.nfs remotetarget dir [-rvVwfnsh] [-o nfsoptions]
options:
	-r		Mount file system readonly
	-v		Verbose
	-V		Print version
	-w		Mount file system read-write
	-f		Fake mount, do not actually mount
	-n		Do not update /etc/mtab
	-s		Tolerate sloppy mount options rather than fail
	-h		Print this help
	nfsoptions	Refer to mount.nfs(8) or nfs(5)

docker@minishift:~$ sudo /sbin/mount.nfs -V ''     # Empty string after -V
mount.nfs: (linux nfs-utils 1.3.3)

docker@minishift:~$ sudo /sbin/mount.nfs -V /
mount.nfs: (linux nfs-utils 1.3.3)

See minishift/minishift-ci-jobs#1 (comment)

After spiting from minishift/deploy we have minikube directory, I don't see any use case for it and I think it's fine to remove it. WDYT?

I think we should we docker version (similar to upstream boot2docker) + a minor version e.g. 1 , 2, 3 etc as the release version e.g. 1.12.3-1

At this point we are running relatively old version of docker i.e. 1.12.3 and we should update it latest docker i.e. https://github.com/boot2docker/boot2docker/releases/tag/v1.13.1

At the moment we write by concatenating to the automount file.

it might be better to replace this with echoing a full file, as what is done in our CentOS ISO. This allows for a better insight to what happens and control over how links/mounts are done. See #57, #46, etc

I would also suggest to move the bootlocal.sh script to scripts/handle-user-data to make the two versions of images more consistent from a developer's viewpoint.

Currently b2d images doesn't have docker options persistent and restart will overwrite whatever configuration we change during a session. We need a persistent docker config to expose internal openshift registry and for proxy stuff.

It will be great if we can upgrade to the latest version of boot2docker so that we can use latest docker verson 17.09.0-ce in minishift

Currently, the header created with #HEADER Title is not working.

This might be due to [Github migration to Kramdown (markdown engine)]https://github.com/blog/2100-github-pages-now-faster-and-simpler-with-jekyll-3-0) which has affected READMEs too in recent times.

See https://github.com/blog/2333-a-formal-spec-for-github-flavored-markdown.

Check https://github.github.com/gfm/#leaf-blocks section 4.2ATX headings.

On our current master, we are not able to build the iso since it failed to build the intermediate container.

The issue is with the https://github.com/minishift/minishift-b2d-iso/blob/master/iso/conntrack.sh#L23 , we need to update http to https.

Documentation for release process is missing.

Right now all targets in the Makefile are phony. With a bit of refactoring we can do "proper" dependency checks, so that 'make' will not rebuild the ISO if none of the underlying build files has changed.

See also minishift/minishift#510
This needs investigation of whether it is possible and whether it can resolve minishift/minishift#510

With 3.10.x, the default directory for a remote docker daemon is /var/lib/origin which we can't change so this should be bind mounted properly.