I will just show how an immutable zone gets installed.
On this example the zone won't have any specific services.
Well, at a minimum, for convenience, I choose make it a NIS client.
On a more real scenario, I would further refine the configuration profile.
For instance, I could add other pre-configured SMF services.
I assume all the premises of the aforementioned posts.
The immutable zone configuration and configuration profile are ready.
In fact, there are more than one installation method.
It can happen through:
- Automated Installer (AI); not shown on this post;
- From the scratch;
- Cloning;
There's nothing really special about installing "from the scratch":
# zoneadm -z zone-1 install -c /tmp/zone-1.xml
...
I like the cloning method because it's faster and tends to save space:
# zoneadm -z zone-1 clone -c /tmp/zone-1.xml template-zone
...
NOTE
The argument to the -c option must be an absolute path.Here's the zone-1 zone's console on the 1st boot:
template-zone must not be an immutable zone already.
# zlogin -C zone-1
[Connected to zone 'zone-1' console]
From another terminal just boot the zone:
# zoneadm -z zone-1 boot
Now go back to the zone's console and watch:
[NOTICE: Read-only zone booting up read-write]
SunOS Release 5.11 Version 11.1 64-bit
Copyright (c) 1983, 2012, Oracle and/or its affiliates...
Hostname: unknown
Hostname: zone-1
[NOTICE: This read-only system transiently booted read/write]
[NOTICE: Now that self assembly has been completed, the system is rebooting]
[NOTICE: Zone rebooting]
SunOS Release 5.11 Version 11.1 64-bit
Copyright (c) 1983, 2012, Oracle and/or its affiliates...
Hostname: zone-1
zone-1 console login:
It's amazing how the system detects I'm installing an immutable zone and then upon installation boots the zone in read-write mode and after installation finishes, the zone is automatically rebooted to assume its immutability state. This saves administrators some work and makes sure no interactions are required.
