| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149 | 
.. _snap: https://snapcraft.io.. _snapcraft LXD: https://snapcraft.io/lxd.. _LXC/LXD Image Server: https://uk.images.linuxcontainers.org/.. _LXC: https://linuxcontainers.org/lxc/introduction/.. _LXD: https://linuxcontainers.org/lxd/introduction/.. _`LXD@github`: https://github.com/lxc/lxd.. _archlinux: https://www.archlinux.org/.. _lxc.sh:================``utils/lxc.sh``================.. sidebar:: further reading   - snap_, `snapcraft LXD`_   - LXC_,  LXD_   - `LXC/LXD Image Server`_   - `LXD@github`_With the use of *Linux Containers* (LXC_) we can scale our tasks over a stack ofcontainers, what we call the: *lxc suite*.  The *searx suite*(:origin:`lxc-searx.env <utils/lxc-searx.env>`) is loaded by default, every timeyou start the ``lxc.sh`` script (*you do not need to care about*).Before you can start with containers, you need to install and initiate LXD_once::  $ snap install lxd  $ lxd init --autoTo make use of the containers from the *searx suite*, you have to build the:ref:`LXC suite containers <lxc.sh help>` initial.  But be warned, **this mighttake some time**::  $ sudo -H ./utils/lxc.sh buildA cup of coffee later, your LXC suite is build up and you can run whatever taskyou want / in a selected or even in all :ref:`LXC suite containers <lxc.shhelp>`.  If you do not want to build all containers, **you can build justone**::  $ sudo -H ./utils/lxc.sh build searx-ubu1804*Good to know ...*Each container shares the root folder of the repository and the command``utils/lxc.sh cmd`` **handles relative path names transparent**, compare outputof::  $ sudo -H ./utils/lxc.sh cmd -- ls -la Makefile  ...In the containers, you can run what ever you want, e.g. to start a bash use::  $ sudo -H ./utils/lxc.sh cmd searx-ubu1804 bash  INFO:  [searx-ubu1804] bash  root@searx-ubu1804:/share/searx#If there comes the time you want to **get rid off all** the containers and**clean up local images** just type::  $ sudo -H ./utils/lxc.sh remove  $ sudo -H ./utils/lxc.sh remove images.. _lxc.sh install suite:Install suite=============To install the complete :ref:`searx suite (includes searx, morty & filtron)<lxc-searx.env>` into all LXC_ use::  $ sudo -H ./utils/lxc.sh install suiteThe command above installs a searx suite (see :ref:`installation scripts`).  Toget the IP (URL) of the filtron service in the containers use ``show suite``command.  To test instances from containers just open the URLs in yourWEB-Browser::  $ sudo ./utils/lxc.sh show suite | grep filtron  [searx-ubu1604]  INFO:  (eth0) filtron:    http://n.n.n.246:4004/ http://n.n.n.246/searx  [searx-ubu1804]  INFO:  (eth0) filtron:    http://n.n.n.147:4004/ http://n.n.n.147/searx  [searx-ubu1910]  INFO:  (eth0) filtron:    http://n.n.n.140:4004/ http://n.n.n.140/searx  [searx-ubu2004]  INFO:  (eth0) filtron:    http://n.n.n.18:4004/ http://n.n.n.18/searx  [searx-fedora31]  INFO:  (eth0) filtron:    http://n.n.n.46:4004/ http://n.n.n.46/searx  [searx-archlinux]  INFO:  (eth0) filtron:    http://n.n.n.32:4004/ http://n.n.n.32/searxTo :ref:`install a nginx <installation nginx>` reverse proxy for filtron andmorty use (or alternatively use :ref:`apache <installation apache>`)::    sudo -H ./utils/lxc.sh cmd -- FORCE_TIMEOUT=0 ./utils/filtron.sh nginx install    sudo -H ./utils/lxc.sh cmd -- FORCE_TIMEOUT=0 ./utils/morty.sh nginx installRunning commands================**Inside containers, you can use make or run scripts** from the:ref:`toolboxing`.  By example: to setup a :ref:`buildhosts` and run theMakefile target ``test`` in the archlinux_ container::  sudo -H ./utils/lxc.sh cmd searx-archlinux ./utils/searx.sh install buildhost  sudo -H ./utils/lxc.sh cmd searx-archlinux make testSetup searx buildhost=====================You can **install the searx buildhost environment** into one or all containers.The installation procedure to set up a :ref:`build host<buildhosts>` takes itstime.  Installation in all containers will take more time (time for another cupof coffee).::  sudo -H ./utils/lxc.sh cmd -- ./utils/searx.sh install buildhostTo build (live) documentation inside a archlinux_ container::  sudo -H ./utils/lxc.sh cmd searx-archlinux make docs.clean docs.live  ...  [I 200331 15:00:42 server:296] Serving on http://0.0.0.0:8080To get IP of the container and the port number *live docs* is listening::  $ sudo ./utils/lxc.sh show suite | grep docs.live  ...  [searx-archlinux]  INFO:  (eth0) docs.live:  http://n.n.n.12:8080/.. _lxc.sh help:Overview========The ``--help`` output of the script is largely self-explanatory:.. program-output:: ../utils/lxc.sh --help.. _lxc-searx.env:searx suite===========.. literalinclude:: ../../utils/lxc-searx.env   :language: bash
 |