Skip to content
Robin Doer edited this page May 17, 2024 · 1 revision

Perhaps the easiest way to try out the nuts tool is via a Docker container:

docker pull dorobin/nuts

The container can then simply be run with docker run. The following command opens a shell in the container:

docker run -it dorobin/nuts bash

The nuts tool can be started in the shell:

root@1ae428e28a92:/# whereis nuts
nuts: /usr/local/bin/nuts
root@1ae428e28a92:/# nuts --help
Usage: nuts [OPTIONS] <COMMAND>

Commands:
   plugin Configure plugins
   container General container tasks
   archive An archive on top of the container
   help Print this message or the help of the given subcommand(s)

Options:
   -v, --verbose... Enable verbose output. Can be called multiple times
   -q, --quiet Be quiet. Don't produce any output
   -h, --help Print help
   -V, --version Print version

The nuts tool stores its configuration and container data in the /root/.nuts directory. Due to the nature of Docker, all of this data is lost when the container is closed. To prevent this, the /root/.nuts directory can be mounted in the container of the Docker host:

docker run -it -v $HOME/.nuts:/root/.nuts dorobin/nuts bash

Thus, the .nuts directory in the home directory of the Docker host is mounted in the /root/.nuts directory in the Docker container. The data is no longer lost when closing the Docker container and can be reused.

Clone this wiki locally