Pretty vague on the details. I’m not familiar with portainer. Is this a public ip that is assigned or one you want to have the same internally to the containers?
this post was submitted on 27 Jun 2023
4 points (100.0% liked)
Docker
1080 readers
1 users here now
founded 1 year ago
MODERATORS
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
Ok. I did a little reading and I actually have used portainer, I just forgot, but not how you are using it. I can’t offer you a quick fix, but based on some assumptions I can offer some unsolicited advice.
It looks like you want a CI/CD framework. What you’re doing sounds pretty straightforward and almost all projects are using some kind of automated tooling for this that gives you the flexibility you’re looking for.
Everything you want your build to do and be, minus secrets, should be in the repo.
it should only be a personal state of the art preview thing. a complete ci/cd would may be a overkill
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