Skip to main content
Star us on GitHub Star

Local - No Docker

This page will show you how to get your Ziti Network up and running quickly and easily, entirely locally. Since you'll be running everything locally, you'll have no issues communicating between network components. All the processes will run locally, and you'll be responsible for starting and stopping them when you want to turn the overlay network on or off.

Prerequisites​

note

Make sure you have jq and curl installed before running the expressInstall one-liner.

There is not much preparation necessary to getting up-and-running locally. At this time, this guide expects that you'll be running commands within a bash shell. If you're running Windows, you will need to make sure you have Windows Subsystem for Linux installed for now. We plan to provide a Powershell script in the future, but for now the script requires you to be able to use bash. Make sure your local ports 1280, 6262, 10000 are free before running the controller. These ports are the default ports used by the controller. Also ensure ports 10080 and 3022 are open as these are the default ports the edge router will use.

Run expressInstall One-liner​

Running the latest version of Ziti locally is as simple as running this one command:

    source /dev/stdin <<< "$(wget -qO- https://get.openziti.io/quick/ziti-cli-functions.sh)"; expressInstall

This script will perform an 'express' install of Ziti which does the following:

  • download the latest version of the Ziti components (ziti, ziti-controller, ziti-edge-router, ziti-tunnel)
  • extract the components into a predefined location: ~/.ziti/quickstart/$(hostname -s)
  • create a full PKI for you to explore
  • create a controller configuration using default values and the PKI created above
  • create an edge-router configuration using default values and the PKI created above
  • add helper functions and environment variables to your shell (explore the script to see all)

Start the Components​

Once the latest version of Ziti has been downloaded and added to your path, it's time to start your controller and edge router.

Start Your Controller​

startController

Example output:

$ startController
ziti-controller started as process id: 1286. log located at: /home/vagrant/.ziti/quickstart/bullseye/bullseye.log

Verify the Controller is Running​

Assuming you have sourced the script, you will have an environment variable set named $ZITI_EDGE_CONTROLLER_API. After the controller has started, your controller should be listening at that hostname:port combination. You can see what your value is set to by running echo $ZITI_EDGE_CTRL_ADVERTISED. This variable defaults to: $(hostname):1280. Make sure the controller is on and listening and then start the edge router. 

$ echo $ZITI_EDGE_CTRL_ADVERTISED
My-Mac-mini.local.domain:1280

Start Your Edge Router​

Now that the controller is ready, you can start the edge router created with the 'express' process. You can start this router locally by running:

startRouter

Example output:

$ startRouter
Express Edge Router started as process id: 1296. log located at: /home/vagrant/.ziti/quickstart/bullseye/bullseye-edge-router.log

You can verify the edge router is listening by finding the value of $ZITI_EDGE_ROUTER_HOSTNAME:$ZITI_EDGE_ROUTER_PORT. Again, this will default to using $(hostname -s) as the host name and port 3022.

Stopping the Controller and Router​

stopRouter 
stopController

Example output:

$ stopRouter 
INFO: stopped router

$ stopController 
INFO: Controller stopped.

Testing Your Overlay​

At this point you should have a functioning Ziti Network. The script you sourced provides another function to login to your network. Try this now by running zitiLogin. You should see something similar to this:

~ % zitiLogin
Token: 40d2d280-a633-46c9-8499-ab2e005dd222
Saving identity 'default' to ${HOME}/.ziti/quickstart/My-Mac-mini.local.domain/ziti-cli.json

You can now use the ziti CLI to interact with Ziti!. The ziti binary is not added to your path by default but will be available at "${ZITI_BIN_DIR-}/ziti". Add that folder to your path, alias ziti if you like. Let's try to use this command to see if the edge router is online by running: "${ZITI_BIN_DIR-}/ziti" edge list edge-routers.

~ % "${ZITI_BIN_DIR-}/ziti" edge list edge-routers
id: rhx6687N.P    name: My-Mac-mini.local.domain    isOnline: true    role attributes: {}
results: 1-1 of 1

Horray! Our edge router shows up and is online!

Run Your First Service​

You can try out creating and running a simple echo service through ziti by running the first-service tutorial.

~ % "${ZITI_BIN_DIR-}/ziti" edge tutorial first-service

Customizing the Express Install​

You can influence and customize the express installation somewhat if you wish. This is useful if trying to run more than one instance of Ziti locally. The most common settings you might choose to customize would be the ports used or the name of the network.

Configuration File Location​

You can change the location of the configuration files output by adding a parameter to the expressInstall function invocation. However, if you do this you will also need to set other environment variables as well. Please realize that if you change these variables each of the "hostname" variables will need to be addressable:

  • ZITI_CONTROLLER_HOSTNAME
  • ZITI_EDGE_CONTROLLER_HOSTNAME
  • ZITI_EDGE_CONTROLLER_PORT
  • ZITI_EDGE_ROUTER_HOSTNAME
  • ZITI_EDGE_ROUTER_PORT

Here is an example which allows you to put all the files into a folder called: ${HOME}/.ziti/quickstart/newfolder, uses a host named 'localhost', and uses ports 8800 for the edge controller and 9090 for the edge router:

ZITI_CONTROLLER_HOSTNAME=localhost; \
ZITI_EDGE_CONTROLLER_HOSTNAME=localhost; \
ZITI_EDGE_CONTROLLER_PORT=8800; \
ZITI_EDGE_ROUTER_HOSTNAME=localhost;ZITI_EDGE_ROUTER_PORT=9090; \
source ziti-cli-functions.sh; expressInstall newfolder

Sourcing the Env File​

In the case you close your shell and you want to get the same environment variables back into your shell, you can just source the "env" file that is placed into the location you specified. For example, if you ran the example above where the deployed files went to ${HOME}/.ziti/quickstart/newfolder you would find an "env" file at ${HOME}/.ziti/quickstart/newfolder/newfolder.env and source it:

source ${HOME}/.ziti/quickstart/newfolder/newfolder.env

~ % zitiLogin
Token: aa1c7fb0-85d9-4a79-86b2-5df450c5b4de
Saving identity 'default' to ${HOME}/.ziti/quickstart/newfolder/ziti-cli.json

Next Steps​