A bash-based remote control for LXC containers.
This script goal is to ease the common tasks when controlling LXC containers on a machine.
Why this? because is a PITA to constantly type the
--name option while you need it (so it's not an option, it should be a mandatory argument for
It's a manual install. Don't worry, there aren't any hard step.
- Copy the
lxcitedfile somewhere in your
- make sure it's executable (use
- Copy the
- Add the following to your
Trust me on this
This will install the latest master version of lxcited in your home environment.
mkdir -p ~/bin curl -o ~/bin/lxcited https://raw.githubusercontent.com/brunobord/lxcited/master/lxcited curl -o ~/bin/lxcited.autocomplete https://raw.githubusercontent.com/brunobord/lxcited/master/lxcited.autocomplete chmod +x ~/bin/lxcited echo '# LXCITED' >> .bashrc echo 'export PATH=$HOME/bin/:$PATH' >> .bashrc echo 'source $HOME/bin/lxcited.autocomplete' >> .bashrc
Next time you'll run "source .bashrc" (manually or when you'll log in),
lxcited will be available.
If you want to simply update, just re-rerun the two cURL commands.
WARNING: you have to be root to use this tool.
lxcited start what_a_beautiful_container
Get help with:
For more help on a specific command, simply type:
lxcited help destroy
You can autocomplete commands:
$ lxcited st<TAB><TAB> start stop $ lxcited st
... or containers:
$ lxcited start deb<TAB><TAB> debian1 debian2 deborah $ lxcited start deb
Use lxcited along with
For some reasons, when the
lxcited executable is located in you
~/bin or in some other custom path,
sudo can't reach it and you can't run:
If you want to be able to run lxcited with
sudo, instead of installing it in a custom path, you can copy or symlink your file in
/usr/local/bin or any other "well-known path" that will fit the
This piece of software is published under the terms of the WTFPL
See: http://www.wtfpl.net/ for more details, but here is its core term:
- You just DO WHAT THE FUCK YOU WANT TO.