This appears more complicated than I first thought.... Basically, what I did (I may be all wrong): 1) Got a machine with kiwi installed 2) Downloaded every file from there: https://build.opensuse.org/package/show/devel:kubic:images/openSUSE-Tumblewe... and paced them in a directory called MicroOS 3) Changed the repo from the kiwi file to: <repository type="yast2" alias="Tumbleweed" imageinclude="true"> <source path="http://download.opensuse.org/tumbleweed/repo/oss"/> </repository> 4) Tried to run: kiwi-ng --type=oem --profile=hardware-x86_64 --debug system build --description=MicroOS --target-dir=/tmp/MicroOS (no luck, KiwiTypeNotFound: build type oem not found 5) Tried kiwi-ng --type=vmx --profile=hardware-x86_64 --debug system build --description=MicroOS --target-dir=/tmp/MicroOS (to figure out) It ran for a moment, then stopped with: + '[' -f /etc/sysconfig/network/dhcp ']' + echo 'warning: config file /etc/sysconfig/network/dhcp not found' + echo FONT=eurlatgr.psfu + echo '** Rehashing SSL Certificates...' + update-ca-certificates + for i in /usr/lib/rpm/gnupg/keys/gpg-pubkey*asc + rpm --import '/usr/lib/rpm/gnupg/keys/gpg-pubkey*asc' error: /usr/lib/rpm/gnupg/keys/gpg-pubkey*asc: import read failed(2). + true + '[' -x /usr/sbin/add-yast-repos ']' + add-yast-repos + zypper --non-interactive rm -u live-add-yast-repos + rpm -q kubernetes-kubelet + sed -i 's/.*solver.onlyRequires.*/solver.onlyRequires = true/g' /etc/zypp/zypp.conf + sed -i 's/.*rpm.install.excludedocs.*/rpm.install.excludedocs = yes/g' /etc/zypp/zypp.conf + sed -i 's/^multiversion =.*/multiversion =/g' /etc/zypp/zypp.conf + '[' true = true ']' + echo 'creating initial snapper config ...' + cp /etc/snapper/config-templates/default /etc/snapper/configs/root cp: cannot stat '/etc/snapper/config-templates/default': No such file or directory These are the last few line of the run.... don't exactly understand the issue.... Looks like I need some more explanations, unfortunately... Christian -----Original Message----- From: Fabian Vogt <fvogt@suse.de> Sent: Wednesday, March 6, 2019 11:23 AM To: opensuse-kubic@opensuse.org Cc: Tardif, Christian <christian.tardif@bell.ca> Subject: Re: [opensuse-kubic] MicroOS custom image build Hi, Am Mittwoch, 6. März 2019, 17:08:33 CET schrieb Tardif, Christian:
Hi,
We're starting to look at MicroOS as the base OS for our Kubernetes stacks. And as we're now using RKE to deploy k8s, we're stuck with Docker right now.
Added to this, we have other things to customize in order to ease the OS deployment (mostly targeting, but not limited to bare metal deployment)
Two questions here: 1) Can I (I assume yes) leverage kiwi to build a raw image (as our metal deployer requires raw image)? If so, I haven't found how to do it in the available docs
Yes, that should work fine. Currently we're not building any raw images for x86_64, but for RaspberryPi and Pine64 it works. It might be enough to set "image='oem'" in the kiwi image type. You could also convert the qcow2 images to .raw if you don't need the automatic filesystem expansion. https://opensource.suse.com/kiwi/building/build_oem_disk.html https://build.opensuse.org/package/view_file/devel:kubic:images/openSUSE-Tum... Cheers, Fabian
2) Providing that everything is automated and standardized, using cloud-init NoCloud datasource is not an option (as it's unlikely we'll be having a connected unpartitioned disk to hold the cloud-init configuration), and I haven't been able to make the LocalDisk datasource (again, I most probably just haven't the docs required to make it work).
Thanks!
Christian
-- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org -- To unsubscribe, e-mail: opensuse-kubic+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kubic+owner@opensuse.org