From 4eddd7f7c1c31f341711f7aea241fd0474929be0 Mon Sep 17 00:00:00 2001 From: konsthol Date: Tue, 5 Sep 2023 18:09:18 +0300 Subject: [PATCH] Feed. You. Stuff. No time. --- assets/pages/demo/demo.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/assets/pages/demo/demo.md b/assets/pages/demo/demo.md index 1a61a5c..282850b 100644 --- a/assets/pages/demo/demo.md +++ b/assets/pages/demo/demo.md @@ -62,4 +62,8 @@ You can also specify a port with the `--port` flag. `python3 secdep.py -P aws -c -n test-node -s t3.micro -i ami-08869bacfa1188ec9 --yes --docker_compose --deploy nginx` -Note: The docker-compose.yml file has to be in the same directory as the script and be named as `docker-compose.yml`. Also if it contains a volumes section, make sure thay the left side path before the ":" corresponting to the host path is not owned by root but by your user +Note: The docker-compose.yml file has to be in the same directory as the script and be named as `docker-compose.yml`. Also if it contains a volumes section, make sure thay the left side path before the ":" corresponting to the host path is not owned by root but by your user and if using portainer make sure to enter the full path in the web editor + +Additional Note: Portainer uses docker compose instead of docker-compose so the only viable option to deploy docker-compose.yml files is from the --docker_compose flag + +Additional Note 2: By deploying a docker-compose.yml file using the --docker_compose flag, the needed ports will be allowed by the firewall for usage. But by deploying a docker image through portainer one should then `sudo ufw allow needed_port` and `sudo ufw reload` for them to be usable