Added doc and fixes - bridge support

This commit is contained in:
Stefano Marinelli
2021-12-02 15:22:08 +01:00
parent ec1356df08
commit d951a70b30
3 changed files with 14 additions and 1 deletions

View File

@@ -22,6 +22,7 @@ Christer Edwards [christer.edwards@gmail.com]
- Petru T. Garstea
- Sven R.
- Tobias Tom
- Stefano Marinelli
### Special thanks
Software doesn't happen in a vacuum. Thank you to the following people who may

View File

@@ -109,6 +109,18 @@ To define a default route / gateway for all VNET containers define the value in
This config change will apply the defined gateway to any new containers.
Existing containers will need to be manually updated.
Virtual Network (VNET) on External Bridge
--------------------------------------
To create a VNET based container and attach it to an external, already existing bridge, use the `-B` option, an IP/netmask and
external bridge.
.. code-block:: shell
bastille create -B azkaban 12.1-RELEASE 192.168.1.50/24 bridge0
Bastille will automagically create the interface, attach it to the specified bridge and connect /
disconnect containers as they are started and stopped.
The bridge needs to be created/enabled before creating and starting the jail.
Public Network
==============

View File

@@ -43,7 +43,7 @@ usage() {
-L | --linux -- This option is intended for testing with Linux jails, this is considered experimental.
-T | --thick -- Creates a thick container, they consume more space as they are self contained and independent.
-V | --vnet -- Enables VNET, VNET containers are attached to a virtual bridge interface for connectivity.
-B | --bridge -- Enables VNET, VNET containers are attached to a specified, already existing local bridge.
-B | --bridge -- Enables VNET, VNET containers are attached to a specified, already existing external bridge.
EOF
exit 1