#docker

They do not need to communicate. They *do* share a common (very important) config file, which is why they're part of the same stack

@Celmor

btw. if you prefix a nick by @ it won't highlight it for that user, at least on certain clients

"why am I even having this problem?" having what problem, just expose the services differently (using port mapping, or however the 3rd party accesses it)

can regular bash scripts be used in same way as docker compose,like whats the advantages of compose in any case?

you mean docker-compose? it is a docker client and automates a lot of stuff, it doesn't call `docker` commands itself but communicates with the daemon directly, but you could probably get the same behavior using an extensive bash script

Celmor: sorry yes i ment docker-compose,im abit new to linux and docker in general,ive done some lxc but not so much docker,just saw i might be able to utilize bash scripts instead ,thanks for answers m8 (,")

Celmor: maybe it will use less resources on larger environments using compose since it communicate directly with daemon

Greyztar: https://github.com/p8952/bocker this i knew of from some time ago.. not sure how it works today

also the container configuration is maintained in a yaml formatted file for docker-compose which is also compatible with docker swarm (e.g. docker deploy), you would have to also implement reading that file if you wanted to replace it with a bash script

geggam: cheers nice one

if you want to manage multiple containers, i.e. a stack, you usually use docker-compose, if not already swarm mode

Celmor: seems fair yes thanks for input

yw

Celmor: Let me rephrase. My nodes A and B are on two separate Docker networks and have two IP addresses. However, they both expose port 80. If I try to access node B through port 80, I get node A instead

guess that's the internal load balancer, not sure how to configure that

do you have them on an overlay network?

Celmor: That's the default, right? If so, then yes (overlay driver, swarm scope)

try different network driver if you don't need to connect them anyway, or even host network_mode if swarm allows it

swarm doesn't allow network_mode

can you use an alternate network driver then?

Not bridge. "Only networks scoped to the swarm can be used, such as those created with the overlay driver."

So I have to figure out how to configure the overlay driver, then

Anyone tried an image pull in the last few minutes? I am getting 503's

I'm doing `docker pull postgres` to try to update my postgres image but I'm getting a 503 error?

works fine for me

right okay, but how do I fix it?

maybe flush dns cache

oh, seems to be working now

maybe it was dns

lol the dns meme

Status update: We had a brief outage of registry authentication service which would've disallowed any pushes or pulls. This has since been fixed and we are continuing to monitor the situation. Sorry for the inconvenience. -- https://status.docker.com/pages/incident/533c65...

oh interesting, so it wasn't dns

and I am back