Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to access containers via container name and exposed port(internal port without mapping to external) , running in single pod(multi-container) #4

Open
neetra opened this issue Apr 9, 2020 · 0 comments

Comments

@neetra
Copy link

neetra commented Apr 9, 2020

Problem:
I have two applications say applicationA, applicationB.

Using Docker compose.yml:
version: ‘3.4’

services:
applicationa:
environment:
- ASPNETCORE_ENVIRONMENT=Development

ports:
  - "7001:80"  

applicationb:
environment:
- ASPNETCORE_ENVIRONMENT=Development
In dockerfile of applicationa (Exposed port 80), applicationb(exposed port 5000)
Exposed port of applicationB is not mapped to external port thus it is not accessible directly
ApplicationA access applicationB via http://containername:containerexposedport i.e http://applicationb:5000

Using Minikube:
Deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: appaappb-deployment
labels:
app: appaappb
spec:
replicas: 1
selector:
matchLabels:
app: appaappb
template:
metadata:
labels:
app: appaappb
spec:
containers:

  • name: appa
    image: appa:latest
    env:
  • name: ASPNETCORE_ENVIRONMENT
    value: “Development”
    ports:
  • containerPort: 80
    imagePullPolicy: Never
    containers:
  • name: appb
    image: appb:latest
    env:
  • name: ASPNETCORE_ENVIRONMENT
    value: “Development”
    ports:
  • containerPort: 5000
    imagePullPolicy: Never

Service (Map external port)
kubectl expose pod appaappb-deployment-8656cfcdff-wd4hv --name=appaappbservice --type=“NodePort” --target-port 80 --port 80

Now as appA and appB are not in same docker network appA cannot access appB via container name and container internal port

So how to access appB in appA ?

information:
Minikube version:v1.9.2
Docker version: 19.0.3

@neetra neetra changed the title Containers not accessible via container name , running in single pod(multi-container) How to access containers via container name and exposed port(internal port without mapping to external) , running in single pod(multi-container) Apr 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant