Enterprise FAQ and Tips¶
Docker and sudo¶
If not running as root
, all your docker
and docker-compose
commands will require sudo
in front of them, which may
get repetitive.
Examine permissions to /var/run/docker.sock
. They will usually look
like this:
srw-rw---- 1 root docker 0 May 12 11:52 /var/run/docker.sock
Notice that in this example, both root
and group docker
have access
to read and write to this socket. Docker command line tools use this socket
to talk to Docker daemon, and whichever user launches them requires rw
to that path.
Therefore, solution to not requiring sudo
in this case would be to either
add your user to docker
group, or run a root shell and launch all your
docker commands from that root shell.
Data Location¶
If you’re searching for Data Directory of a Docker stack, it’s always
configured via the DATA_ROOT
variable of your .env
file of the
corresponding stack.
By default, it’ll be /var/lib/omni/<subdir>
, with <subdir>
depending
on a particular stack (ie, nucleus-data
, nucleus-cache-data
, etc).
Documentation on Configuring .env Files¶
Documentation on parameters, meaning, and effect of said parameters configured
via our .env
files that come with our stacks is located within the .env
files themselves.
All the comments in there are the documentation on parameters they are placed next to.
One reason for documenting .env
files within themselves rather than
here is that we can have descriptive narrative coupled to parameters
in one place.
Otherwise, we may create confusion in which parameters can be used with which
versions of the .env
files.