bumping poms
This commit is contained in:
@@ -62,8 +62,6 @@ 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 and if using portainer make sure to enter the full path in the web editor
|
||||
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 that 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
|
||||
Additional Note: 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 or docker-compose.yml file through portainer one should then `sudo ufw allow needed_port` and `sudo ufw reload` for them to be usable or `firewall-cmd --permanent --add-port=needed_port` and `sudo firewall-cmd --reload` depending on the distribution
|
||||
|
||||
Reference in New Issue
Block a user