Hi all. I've successfully deployed an app with Docker using 3 containers: app, DB and nginx. Now I'd like to do the same on the same host machine but for another client. Everything must be separated. Is it enough to create a different network or do I have to do something else?
Can use different nodes for different clients on k8s with same configurations.
Hello all, I want to share with you MiroTalk.
WebRTC P2P/SFU, Simple, Secure, Scalable, Fast, Real-Time Video Conferences Up to 4k and 60fps, compatible with all browsers and platforms.
Can be run in Docker as well.
i have a question about binding folders.
at the moment i try to deploy a nextcloud container.
i want to bind the config folder:
- nextcloud:/var/www/html - /opt/portainer/nextcloud/data:/var/www/html/data:rw - /opt/portainer/nextcloud/config:/var/www/html/config:rw
if i do that, no config will create by deploying the containers. the folder stay empty. how i can solve it?
if i dont bind the config folder and look into the container, i see many config files.
i'm not sure that this is the spot to ask this, but i'll try it anyway
i'm having a prometheus instance in a docker and another docker with the alertmanager.
My problem is that prometheus can't connect to the alertmanager. All services are started with a docker-compose, but when running i get the following errors:
prometheus | ts=2022-07-05T09:35:14.522Z caller=notifier.go:526 level=error component=notifier alertmanager=http://alertmanager:9460/api/v2/alerts count=6 msg="Error sending alert" err="Post \"http://alertmanager:9460/api/v2/alerts\": dial tcp 172.26.0.5:9460: connect: connection refused"
All serices are in the same networkt by default because of the docker-compose, but i checked it with
docker network inspect. It's just very unclear for me, if this is a docker or prometheus/alertmanager problem.