coreprocess / linux-unattended-installation Goto Github PK

dos2unix: converting file ./isolinux.cfg to Unix format...
./build-iso.sh: line 36: patch: command not found
root@TestUbuntu-VM:~/linux-unattended-installation-master/ubuntu/18.04#

Image running: Ubuntu 18.04.2 LTS (GNU/Linux 4.15.0-46-generic x86_64)

Can you please tell me what dependency I'm missing? I installed the recommended ones from the readme.md.

Cheers!

The machine I'm installing to is a dev machine and I don't care what drives I reformat.
It does have Linux installed to the nvme drive already. Erasing is no problem here.

Drives we have
1 NVME, usually our OS is installed here /dev/nvme0n1
1 SSD, fast archive storage /dev/sdb
1 HDD, slow archive storage /dev/sda

Bios boot order is:
NVME
SSD
HDD is boot disabled

There is a grub partition already because of the pre-existing install.
Maybe this is the source of the issue for me.
A desirable feature for some would be to format all drives first

Unplugging all drives except nvme0n1 and changing the predeed.cfg from /dev/sda to /dev/nvme0n1 has the same issue and hangs at 66% and doesn't go any further

Line 73

### Partitioning
d-i preseed/early_command string umount /media || true
d-i partman-auto/disk string /dev/nvme0n1
 ...

&

Line 99

### Grub
d-i grub-installer/bootdev string /dev/nvme0n1
d-i grub-installer/only_debian boolean true
d-i grub-installer/with_other_os boolean true
 ...

Any thoughts Niklas?
Again, great work!

Hey I am looking forward to an 20.04 LTS Version =)

What I want

• I would like to not have a binary (isohdpfx.bin) in version control system
• I would like to be able to fetch the required binaries on the fly, according to the context (version to fetch for instance)
• If the official binary isohdpfx.bin does not fit my needs, I would like to be able to rebuild it myself in order to be able to control the involved changes made to it

Why I want

• Having a binary in a repository always makes us wondering if this binary is malicious, so moving this part in a clean way to show what we do and how we do is a good way to proof the code innocence and good faith to dear users
• I would like to enhance quality and to improve users adoption of the awesome work done in this repository

Question(s)

• Do you think it is reasonable/achievable to externalize the fetch of this binary?

I followed the instructions like so:

user$ git clone https://github.com/core-process/linux-unattended-installation.git
user$ ./ubuntu/18.04/build-iso.sh /home/user/.ssh/id_rsa.pub /tmp/bootable_ubuntu1804.iso

When trying to burn the iso with Etcher (official ubuntu usb-stick-creation software recommendation) it complains that this is not a bootable iso. I ignored this at first and did it anyway, but wasn't able to boot with this.
Is this meant to create a bootable iso?

Best,
Alex

How to speed up the installation process?
Could I use a normal ISO instead of netboot mini.iso to speed up installation?

Thanks.

Hello, just created the new ISO file and used in a VM but can't find the username and password that has been used in the installation process.

uisautomation@8a01944

Hello there,

Not sure this is something that has to do with your tooling or with the Ubuntu installation process, but we have bumped into a small problem when using the 18.04 LTS installation on two new machines with 2TB of storage.

The volume group called main (/dev/mapper/main-root) is not sized to use the whole storage. Instead it only uses ~1TB.
This can easily be solved manually after the installation, so it isn't a big deal, but I thought I would flag it anyway.

Cheers,

eighti@console:~/Downloads/linux-unattended-installation-master/ubuntu/18.04$ sudo ./build-iso.sh 
[sudo] password for eighti: 
--2018-07-16 19:28:01--  http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/mini.iso
Resolving archive.ubuntu.com (archive.ubuntu.com)... 91.189.88.162, 91.189.88.149, 91.189.88.161, ...
Connecting to archive.ubuntu.com (archive.ubuntu.com)|91.189.88.162|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 67108864 (64M) [application/x-iso9660-image]
Saving to: ‘./netboot.iso’

./netboot.iso       100%[===================>]  64.00M  9.98MB/s    in 8.4s    

2018-07-16 19:28:10 (7.58 MB/s) - ‘./netboot.iso’ saved [67108864/67108864]

./build-iso.sh: line 30: : command not found
eighti@console:~/Downloads/linux-unattended-installation-master/ubuntu/18.04$ ls
build-disk.sh  build-iso.sh  custom

Sorry if I am missing something simple

It works with netboot.iso perfectly thank you!

I tried to replace netboot.iso with ubuntu-18.04-server-amd64.iso but ran into two issues so far.

1. The patching doesn't seem to work
2. cat: /tmp/tmp.oEoTzfiQlV/initrd.gz: No such file or directory

Not sure what is going on.

Hi there,

I know it's probably a bit out of scope, but would you consider the option of accepting at least two ssh public keys?

Thanks

The URL to the .iso is outdated - something along the lines of this
should be implemented [see lines 68-78]

#get the latest versions of Ubuntu LTS

tmphtml=$tmp/tmphtml
rm $tmphtml >/dev/null 2>&1
wget -O $tmphtml 'http://releases.ubuntu.com/' >/dev/null 2>&1

prec=$(fgrep Precise $tmphtml | head -1 | awk '{print $3}')
trus=$(fgrep Trusty $tmphtml | head -1 | awk '{print $3}')
xenn=$(fgrep Xenial $tmphtml | head -1 | awk '{print $3}')
bion=$(fgrep Bionic $tmphtml | head -1 | awk '{print $3}')

So this is really minor but on a debian install genisoimage is the name of mkisofs.

Basically they are the same really but not sure why one is named mkisofs and one is called genisoimage.

What would be a good way to detect if you have either of them and use it?

See #12

Hello,

there is a bug in the netinstall workflow of Ubuntu 16.04.
LUI hits this aswell, here are bug reports in launchpad.
https://bugs.launchpad.net/ubuntu/xenial/+source/linux/+bug/1820419
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820366
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1766728

I'm able to install v18. How can I login? What are the login credentials?

Newer hardware often prefers UEFI, some of it doesn't even include a legacy BIOS mode.
This would also be helpful to those wishing to do minimal/task specific Desktop installs using the netboot image.

Its been known this is possible to do with the netboot mini.iso for a good while, and its curious that canonical haven't included it as part of the image build process yet.
See:- https://askubuntu.com/questions/738305/why-doesnt-the-minimal-image-support-uefi
and https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1429030

This should be quite possible to add as part of the build-iso.sh script as it does unpack the source iso anyway.

Preseed would also need adjustment to match the manual steps described here:- https://www.onetransistor.eu/2015/12/install-ubuntu-minimal-cd-uefi-enabled.html

when adding a ssh key, it needs to be relative to the temp dir.
So I made myself an enhancement to the build-iso.sh script, that I would like to share (tested on my macbook):

function getRealPath {
    path=$1
    perl << EOF
#!/usr/bin/perl
use Cwd 'abs_path';
\$realfilepath = abs_path("$path");
print "\$realfilepath\n";
EOF
}


# get parameters
SSH_PUBLIC_KEY_FILE=${1:-"$HOME/.ssh/id_rsa.pub"}
TARGET_ISO=${2:-"`pwd`/ubuntu-18.04-netboot-amd64-unattended.iso"}
# get realpath of public key
SSH_PUBLIC_KEY_FILE=$(getRealPath $SSH_PUBLIC_KEY_FILE)
# get realpath of target iso file
TARGET_ISO=$(getRealPath $TARGET_ISO)