Alex-Devera/tpotce
1
0
Fork 0
mirror of https://github.com/telekom-security/tpotce.git synced 2025-07-01 12:32:12 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Update README.md

Browse source
This commit is contained in:
Domenico Del Giudice 2025-03-02 12:54:03 +01:00 committed by GitHub
parent dad760f3f9
commit 6e00d18508
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 25 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
README.md
View file

@ -140,6 +140,7 @@ To get things up and running just follow these steps:
``` ```
docker compose up -d docker compose up -d
``` ```
Before starting T-Pot, make sure Docker is running on your system.
10. During the first time running `docker-compose up`, you may encounter some issues. Check the [Installation Issues](#installation-issues) section to solve them. 10. During the first time running `docker-compose up`, you may encounter some issues. Check the [Installation Issues](#installation-issues) section to solve them.
11. To Stop T-Pot press: `CTRL-C` (it if was running in the foreground) and / or `docker compose down -v` to stop T-Pot entirely. 11. To Stop T-Pot press: `CTRL-C` (it if was running in the foreground) and / or `docker compose down -v` to stop T-Pot entirely.
@ -239,6 +240,19 @@ htpasswd -n -b "tsec" "tsec" | base64 -w0
``` ```
Copy the generated string and manually replace the WEB_USER value in the .env file. Copy the generated string and manually replace the WEB_USER value in the .env file.
#### ⚠️ Issue 5: Missing Directories in T-Pot Initialization
**Issue:** When running `docker compose up`, you may see the following lines in the T-Pot init logs:
```
tpotinit | # Updating permissions ...
tpotinit |
tpotinit | chmod: /data/nginx/conf: Permission denied
tpotinit | chmod: /data/nginx/cert: Permission denied
...
```
**Solution:** To correct this and other issues of the same type, run:
```sh
chmod -R 770 data
```
--- ---
<a name="management-tips"></a> <a name="management-tips"></a>
### 2.2 Management Tips 🛟 ### 2.2 Management Tips 🛟
@ -272,7 +286,17 @@ Copy the generated string and manually replace the WEB_USER value in the .env fi
```sh ```sh
docker exec -it --user root <container_id> /bin/sh docker exec -it --user root <container_id> /bin/sh
``` ```
Or 7. **Prune Unused Networks**: If you encounter network issues, you can remove all unused networks with the following command:
```sh
docker network prune
```
This command will prompt for confirmation before deleting all unused networks.
8. **Restart Containers**: Sometimes, simply restarting the containers can resolve issues. You can do this by bringing the containers down and then up again:
```sh
docker-compose down && docker-compose up
```
This command stops and removes the containers, then recreates and starts them.
--- ---
<a name="testing"></a> <a name="testing"></a>