2020-07-13 19:27:23 -06:00
|
|
|
======
|
2018-11-24 20:07:20 -07:00
|
|
|
create
|
|
|
|
|
======
|
|
|
|
|
|
|
|
|
|
Bastille create uses any available bootstrapped release to create a
|
2019-11-20 19:16:21 -07:00
|
|
|
lightweight container system. To create a container simply provide a name,
|
2018-11-24 20:07:20 -07:00
|
|
|
bootstrapped release and a private (rfc1918) IP address.
|
|
|
|
|
|
|
|
|
|
- name
|
|
|
|
|
- release
|
|
|
|
|
- ip
|
2019-11-20 18:54:05 -07:00
|
|
|
- interface (optional)
|
2018-11-24 20:07:20 -07:00
|
|
|
|
|
|
|
|
.. code-block:: shell
|
|
|
|
|
|
2019-11-20 18:54:05 -07:00
|
|
|
ishmael ~ # bastille create folsom 11.3-RELEASE 10.17.89.10 [interface]
|
2020-04-14 11:52:29 +02:00
|
|
|
|
2019-11-20 18:54:05 -07:00
|
|
|
RELEASE: 11.3-RELEASE.
|
2018-11-24 20:07:20 -07:00
|
|
|
NAME: folsom.
|
2019-11-20 18:54:05 -07:00
|
|
|
IP: 10.17.89.10.
|
2018-11-24 20:07:20 -07:00
|
|
|
|
2019-11-20 19:16:21 -07:00
|
|
|
This command will create a 11.3-RELEASE container assigning the 10.17.89.10 ip
|
2018-11-24 20:07:20 -07:00
|
|
|
address to the new system.
|
|
|
|
|
|
2019-11-20 19:16:21 -07:00
|
|
|
I recommend using private (rfc1918) ip address ranges for your container. These
|
2019-11-20 18:54:05 -07:00
|
|
|
ranges include:
|
2018-11-24 20:07:20 -07:00
|
|
|
|
|
|
|
|
- 10.0.0.0/8
|
|
|
|
|
- 172.16.0.0/12
|
|
|
|
|
- 192.168.0.0/16
|
|
|
|
|
|
2019-11-20 18:54:05 -07:00
|
|
|
Bastille does its best to validate the submitted ip is valid. This has not been
|
|
|
|
|
thouroughly tested--I generally use the 10/8 range.
|
