Update: i solved the problem by using hostnames, inside the nginx container you can use the name of the other container as hostname and it will be resolved automatically
they are all connected to a internal docker network. The ip only matters to my nginx container, which is the only container connected through port bindings. I run on creation something like this: docker run -d --network nginx-bridge --ip 172.172.0.140 ---name main node:latest /project/startup.sh but portainer calls on recreation this: docker run -d --network nginx-bridge ---name main node:latest /project/startup.sh
Sounds good from my point of view. I tried something slightly different with my nextcloud, but it failed. (It could have been due to nextcloud)
I meant, if I buy a domain like sonarr.dev and let it be public under this address. Let's say just for my personal use. Could there raise problems if people see it and report it? Because if I understand it right these tools are to download things (movies/series) via torrent. Or should I just better run it in a local network?
Are they legal to use? Or ist it just a problem if u host it public on the Internet?
How do you deal with inconsistencies while syncing or can't they appear? I just used Plex a while and it didnt worked well for me.
i'd like to mod the docker community
it should only be a personal state of the art preview thing. a complete ci/cd would may be a overkill