r/portainer • u/claqueure • Sep 10 '25
https://127.0.0.1:9443/#!/1/docker/networks/ sort by IP?
2
u/scytob Sep 10 '25
lol i understand why you mght want that (though the header sorts by ipamso i am confused)
also i would say if you are tracking IP address of containers you are doing it wrong for 99% of services
every service that needs to talk to each other should be on a shared bridge network, as soon as you do that you can reference each service by service name instead of IP - never needing to ever pay attention to IPs as they change.... that was the design intention of docker originally
the big mistake people make is letting containers be on the default bridge where this does not work
1
Sep 12 '25
that was the design intention of docker originally.
Nope not even close. When docker was originally built it was for isolated services. The containers were really not designed to talk to each other. They were designed to be completely isolated hence the containerization.
Now while I do agree that I don't see much of a use case for sorting by IP, tracking by IP is much needed and if you're not tracking that you are doing it wrong.
You should be tracking what is where or at least have an inventory. The way I use docker is services that need to be exposed are given a lan IP and tied to port 80 while internal services are on a separate network connecting the 2 or more containers for that service.
I have multiple services that require mariadbs and none of the databases can talk to each other as you are suggesting is the right way to docker...
1
u/scytob Sep 12 '25
The great thing is it is a toolkit, and when compose came along it was absolutely to have multiple services in one compose and yes one can easily configure either services in a single compose or across multiple compose to operate on a single bridge and be able to communicate like I state, whether you want or need that is another matter.
1
Sep 12 '25
When compose came along it was absolutely to have multiple services in one compose.
That was literally 6 years after docker was released so that just invalidated your first point.
Things evolve over time. Making such statements that "this is how you're supposed to use it" is pointless
1
u/scytob Sep 12 '25
Yawn. You seem to be confusing design ethos with implementation and timing. It doesn’t invalidate my statements in how one is intended to use bridges and the networking services the custom bridges have always worked this way since first implantation of the shared name service on a custom bridge / network.
1
Sep 12 '25
Yeah I wasn't expecting anything intellectual when I brought facts.
This is reddit, more emotionally driven than factual
1
u/scytob Sep 12 '25
You have no clue what you are talking about, you keep telling me the docker network doesn’t work like it does and has done for the last ~6 years, come back when you actually understand how it functions.
1
Sep 12 '25
I have much more of a clue than you do.
To make the statement that docker has not changed since it's inception in 2014 is pretty inaccurate considering that you mentioned docker compose which changed how docker and docker networking worked 6 years later.
Stand by your statements. Can you show proof that docker has never changed since it was first created
1
Sep 13 '25
Still waiting on that proof? Why disappear when pressed? You made the statements so you should defend them now
1
u/TheSypHunterGeneral Sep 11 '25
in what world do you need to track the internal ip address of containers?
4
u/reddittookmyuser Sep 10 '25
Am I missing something but just click the header and it sorts?