bbs/clrghouz
1
0
Fork 0
Code Issues 6 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Update Installation

deon 2024-05-26 04:07:52 +00:00
parent b547dd6791
commit 8602e5d2a0
1 changed files with 12 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
Installation.md

@ -60,17 +60,26 @@ uid=500(fred) gid=500(admin) groups=500(admin),10(wheel),27(sudo),498(docker)
## Storage directory
You will want all your data to persist between container restarts. Create a directory to store all the container directory - something like `/srv/docker` (or something you prefer).
You will want all your data to persist between container restarts. Create a directory to store all the container data - something like `/srv/docker` (or something you prefer). The top level directories can be owned as root (`/srv/docker`) with access 755.
## Storage space
Make sure your docker container directory (`/srv/docker`) and `/var/lib/docker` has sufficient space.
Make sure your docker container directory (`/srv/docker/clrghouz`) and `/var/lib/docker` has sufficient space.
If your linux doesnt use mount points, and all your space is mounted under `/`, then you should be OK. But if you do have mount points, then you'll need to have lots of space reserved for those directories.
## Create a directory for Clearing houz
In your storage directory (`/srv/docker`) create a directory to store Clearing houz files (eg:`/srv/docker/clrghouz`). Everything from here on will assume you are working from this directory.
In your storage directory (`/srv/docker/clrghouz`) create a directory to store Clearing houz files (eg:`/srv/docker/clrghouz`). Everything from here on will assume you are working from this directory.
The `clrghouz` dir can be owned with your user id, so that you can get into that dir as your normal logged in user.
EG:
```
> ls -al /srv/docker/clrghouz
drwxr-xr-x 11 fred admin 4096 May 26 13:59 /srv/docker/clrghouz
```
### docker compose