2025-03-01 11:55:36 -07:00
|
|
|
|
=========
|
|
|
|
|
|
Migration
|
|
|
|
|
|
=========
|
|
|
|
|
|
|
|
|
|
|
|
iocage
|
|
|
|
|
|
------
|
|
|
|
|
|
|
2023-10-20 22:28:00 -07:00
|
|
|
|
Stop the running jail and export it:
|
|
|
|
|
|
|
|
|
|
|
|
.. code-block:: shell
|
|
|
|
|
|
|
|
|
|
|
|
iocage stop jailname
|
|
|
|
|
|
iocage export jailname
|
|
|
|
|
|
|
2025-04-20 11:19:18 -05:00
|
|
|
|
Move the backup files (.zip and .sha256) into Bastille backup dir (default:
|
|
|
|
|
|
/usr/local/bastille/backups/):
|
2023-10-20 22:28:00 -07:00
|
|
|
|
|
|
|
|
|
|
.. code-block:: shell
|
|
|
|
|
|
|
2023-10-25 21:36:01 -07:00
|
|
|
|
mv /iocage/images/jailname_$(date +%F).* /usr/local/bastille/backups/
|
2023-10-20 22:28:00 -07:00
|
|
|
|
|
2025-03-01 11:55:36 -07:00
|
|
|
|
for remote systems you can use rsync:
|
2023-10-20 22:28:00 -07:00
|
|
|
|
|
|
|
|
|
|
.. code-block:: shell
|
|
|
|
|
|
|
2023-10-25 21:36:01 -07:00
|
|
|
|
rsync -avh /iocage/images/jailname_$(date +%F).* root@10.0.1.10:/usr/local/bastille/backups/
|
2023-10-20 22:28:00 -07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Import the iocage backup file (use zip file name)
|
|
|
|
|
|
|
|
|
|
|
|
.. code-block:: shell
|
|
|
|
|
|
|
2023-10-25 21:36:01 -07:00
|
|
|
|
bastille import jailname_$(date +%F).zip
|
2023-10-20 22:28:00 -07:00
|
|
|
|
|
2025-04-20 11:19:18 -05:00
|
|
|
|
Bastille will attempt to configure your interface and IP from the
|
|
|
|
|
|
``config.json`` file, but if you have issues you can configure it manully.
|
2023-10-20 22:28:00 -07:00
|
|
|
|
|
|
|
|
|
|
.. code-block:: shell
|
|
|
|
|
|
|
2025-03-01 11:55:36 -07:00
|
|
|
|
bastille edit jailname
|
|
|
|
|
|
ip4.addr = bastille0|192.168.0.1/24;
|
2023-10-20 22:28:00 -07:00
|
|
|
|
|
2025-04-20 11:19:18 -05:00
|
|
|
|
You can use your primary network interface instead of the virtual ``bastille0``
|
|
|
|
|
|
interface as well if you know what you’re doing.
|