Merge pull request #616 from BastilleBSD/issue-527

added iocage migration doc

docs/chapters/migration.rst

@@ -0,0 +1,36 @@
+Stop the running jail and export it:
+
+.. code-block:: shell
+
+     iocage stop jailname
+     iocage export jailname
+
+Move the backup files (.zip and .sha256) into Bastille backup dir (default: /usr/local/bastille/backups/):
+
+.. code-block:: shell
+
+     mv /iocage/images/jailname_$(date +%F).* /usr/local/bastille/backups/
+
+for remote systems you could use rsync:
+
+.. code-block:: shell
+
+     rsync -avh /iocage/images/jailname_$(date +%F).* root@10.0.1.10:/usr/local/bastille/backups/
+
+     
+Import the iocage backup file (use zip file name)
+
+.. code-block:: shell
+
+     bastille import jailname_$(date +%F).zip
+
+Set your new ip address and interface:
+
+.. code-block:: shell
+
+     vim /usr/local/bastille/jails/jailname/jail.conf
+     interface = bastille0;
+     ip4.addr = "192.168.0.1";
+
+
+You can use you primary network interface instead of the virtual bastille0 interface as well if you know what you’re doing.

docs/chapters/subcommands/create.rst

@@ -31,3 +31,12 @@ ranges include:
 
 Bastille does its best to validate the submitted ip is valid. This has not been
 thouroughly tested--I generally use the 10/8 range.
+
+One point to be made about jails.  If you run uname inside a jail you will not
+get the information about the jail, but about the host system.  If you want accurate 
+information about  the jail please use freebsd-version inside the jail.
+
+Also, the MOTD also was reporting the host system instead of the jail.  This 
+caused a lot of confusion for users, so the MOTD was disabled by the use of 
+the .hushlogin file.  This prevents confusing contradictory information to be 
+shown to the user.  

docs/index.rst

@@ -21,6 +21,7 @@ https://docs.bastillebsd.org.
    chapters/jail-config
    chapters/zfs-support
    chapters/gcp
+   chapters/migration
 
    copyright