11-19-2009
thanks for getting back to me, but i fear you missed my point. i am concerned about what will happen if i leave the packages installed after i migrate to the branded zone.
will the container work? will the fact that vfstab be looking for VxFS filesystems cause the container NOT to boot?
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I would like to implement zones in solaris 10 to simulate 2 nodes on a single solaris 10 using zones. Can some one tell me what does it mean by global and non-global zones
Also write what is the use of using non global or global and permissions like read-write on zones.
My requirement... (3 Replies)
Discussion started by: upengan78
3 Replies
2. Solaris
Hello,
I am attempting to install a newly configured Solaris 9 zone using the flash archive image provided on the sun website. Each time I run the install I get a failure during the Postprocess: Creating mount points. Following is the log:
Log File: /var/tmp/s9-zone.install.25457.log... (0 Replies)
Discussion started by: brialt1
0 Replies
3. Solaris
Dear all,
we are trying to install a Solaris10 Branded Zone on a Solaris 11 Express system getting this message:
***The image patch level is downrev for running in a solaris10 branded zone***
The Sparc Solaris 10 system is running Release 11/06 and Patch 119254-70 is installed.
Does the... (0 Replies)
Discussion started by: xunil321
0 Replies
4. Solaris
I have a T5220 running Solaris 10. I have a application that can only run on Solaris 9. I want to build a branded Solaris 9 zone for this application on the Solaris 10 Server.
What steps would I need to accomplish this? (2 Replies)
Discussion started by: soupbone38
2 Replies
5. Solaris
I am trying to create a branded 10 zone on a Solaris 11.1 control domain. I am using a flar image (cpio) from an existing LDOM. Here are the steps taken after flarcreate.
#zonecfg -z <device>
>create -b
>set brand=solaris10
>set zonepath=/zonez/<device>
>set ip-type=exclusive
>add net... (1 Reply)
Discussion started by: aeroforce
1 Replies
6. Solaris
I am trying to get a NFS share on a Solaris 10 branded zone. I have read that this is not possible...but I was hoping someone here could tell me different.
share -F nfs -o ro,anon=0 /dir
This would really surprise me that you cannot do this.
Thanks (2 Replies)
Discussion started by: aeroforce
2 Replies
7. Solaris
All.
I am trying to create a 10 branded zone on a Sol 11.1 T5. The Global is using IPMP...so aggregating is out of the question. Has anyone successfully created a branded zone with IPMP? If they have can you please show me the steps you took to get this to run.
Thanks (4 Replies)
Discussion started by: aeroforce
4 Replies
8. Solaris
Hi,
I want to install branded zone sol 9 in sol 10. I keep getting same error. Please advice me.
Thanks. (12 Replies)
Discussion started by: mzainal
12 Replies
9. Solaris
I am planning to do solaris 11 global zone patching having solaris 10 branded zone. I have a doubts on step 8 specially
Can someone clear my step 8 doubts or if anything wrong between step 1 to step 9 please correct that also as I have pretty good idea about Step 10 mean patching in solaris 10... (2 Replies)
Discussion started by: amity
2 Replies
10. Solaris
So I started with following the example on the omnios page for bhyve (sorry, I can't provide the link because I'm a post shy of the 5 to give a URL):
And found that in the end I was able to create a running bhyve zone, but accessing it via zlogin results in a blank console. I've tried Debian 9... (14 Replies)
Discussion started by: stratacast1
14 Replies
LEARN ABOUT OPENSOLARIS
systemd-nspawn
SYSTEMD-NSPAWN(1) systemd-nspawn SYSTEMD-NSPAWN(1)
NAME
systemd-nspawn - Spawn a namespace container for debugging, testing and building
SYNOPSIS
systemd-nspawn [OPTIONS...] [COMMAND] [ARGS...]
DESCRIPTION
systemd-nspawn may be used to run a command or OS in a light-weight namespace container. In many ways it is similar to chroot(1), but more
powerful since it fully virtualizes the file system hierarchy, as well as the process tree, the various IPC subsystems and the host and
domain name.
systemd-nspawn limits access to various kernel interfaces in the container to read-only, such as /sys, /proc/sys or /sys/fs/selinux.
Network interfaces and the system clock may not be changed from within the container. Device nodes may not be created. The host system
cannot be rebooted and kernel modules may not be loaded from within the container.
Note that even though these security precautions are taken systemd-nspawn is not suitable for secure container setups. Many of the security
features may be circumvented and are hence primarily useful to avoid accidental changes to the host system from the container. The intended
use of this program is debugging and testing as well as building of packages, distributions and software involved with boot and systems
management.
In contrast to chroot(1) systemd-nspawn may be used to boot full Linux-based operating systems in a container.
Use a tool like debootstrap(8) or mock(1) to set up an OS directory tree suitable as file system hierarchy for systemd-nspawn containers.
Note that systemd-nspawn will mount file systems private to the container to /dev, /run and similar. These will not be visible outside of
the container, and their contents will be lost when the container exits.
Note that running two systemd-nspawn containers from the same directory tree will not make processes in them see each other. The PID
namespace separation of the two containers is complete and the containers will share very few runtime objects except for the underlying
file system.
OPTIONS
If no arguments are passed the container is set up and a shell started in it, otherwise the passed command and arguments are executed in
it. The following options are understood:
--help, -h
Prints a short help text and exits.
--directory=, -D
Directory to use as file system root for the namespace container. If omitted the current directory will be used.
--user=, -u
Run the command under specified user, create home directory and cd into it. As rest of systemd-nspawn, this is not the security feature
and limits against accidental changes only.
--private-network
Turn off networking in the container. This makes all network interfaces unavailable in the container, with the exception of the
loopback device.
EXAMPLE 1
# debootstrap --arch=amd64 unstable debian-tree/
# systemd-nspawn -D debian-tree/
This installs a minimal Debian unstable distribution into the directory debian-tree/ and then spawns a shell in a namespace container in
it.
EXAMPLE 2
# mock --init
# systemd-nspawn -D /var/lib/mock/fedora-rawhide-x86_64/root/ /sbin/init systemd.log_level=debug
This installs a minimal Fedora distribution into a subdirectory of /var/lib/mock/ and then boots an OS in a namespace container in it, with
systemd as init system, configured for debug logging.
EXIT STATUS
The exit code of the program executed in the container is returned.
SEE ALSO
systemd(1), chroot(1), debootstrap(8), mock(1)
AUTHOR
Lennart Poettering <lennart@poettering.net>
Developer
systemd 10/07/2013 SYSTEMD-NSPAWN(1)