tiyn/wiki
1
0
Fork 0
mirror of https://github.com/tiyn/wiki.git synced 2025-10-31 02:11:15 +01:00
Code Issues Projects Releases Wiki Activity

docker/nginx: move blocking remote ports to docker

Browse Source
This commit is contained in:
TiynGER
2021-05-21 16:08:41 +02:00
parent 2aef64b420
commit 1fbc10df24
2 changed files with 16 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
wiki/docker.md
View File

@@ -36,3 +36,17 @@ The programs below are useful docker-management systems in different style.
To use Nvidia GPUs with docker you need to install the nvidia-cuda-toolkit. To use Nvidia GPUs with docker you need to install the nvidia-cuda-toolkit.
There is a [guide on marmelab](https://marmelab.com/blog/2018/03/21/using-nvidia-gpu-within-docker-container.html) There is a [guide on marmelab](https://marmelab.com/blog/2018/03/21/using-nvidia-gpu-within-docker-container.html)
that focusses on that topic. that focusses on that topic.
### Block remote port access
If you configured a reverse proxy to a port chances are you don't want the port
to be accessed outside of the proxy.
Especially if you set up a authentication over nginx the open port will avoid
the authentication.
This can be changed at the forwarded docker-service by replacing for example
`-p 7000:7000` with `-p 172.17.0.1:7000:7000`.
This forces the docker container to only expose the port in the docker bridge
network, effectively banning remote access.
If you use [Traefik](./traefik.md) it is not needed, because you don't have to
publish ports to reverse proxy them.

14
wiki/nginx.md
View File

@@ -2,15 +2,5 @@
## Server ## Server
A server can be setup via docker with the [nasourso image](./docker-images/nasourso_-_nginx-certbot-docker-tui.md). A server can be setup via docker with the
[nasourso image](./docker-images/nasourso_-_nginx-certbot-docker-tui.md).
### Block remote port access
If you configured a reverse proxy to a port chances are you don't want the port
to be accessed outside of the proxy.
Especially if you set up a authentication over nginx the open port will avoid
the authentication.
This can be changed at the forwarded docker-service by replacing for example
`-p 7000:7000` with `-p 172.17.0.1:7000:7000`.
This forces the docker container to only expose the port in the docker bridge
network, effectively banning remote access.