Can’t acces Docker container on localhost

Question

I have a front app who uses Angular-cli and i’am trying to check if it works proprely separetly before integrating it in the container core but it seems that i can’t get acces to the localhost. I’am using a macOS Catalina 10.15.7 with Docker Desktop.

And it's not the same problem as others because i already tested before asking my question in stackoverflow so don't put as duplicate, THANK YOU !!

My Dockerfile is build like this:

FROM    node:14-alpine3.12

WORKDIR /app/front

#COPY    ./angular-cli .
COPY    package.json package-lock.json
COPY    . .       

RUN     npm install 
RUN     npm install -g @angular/cli

EXPOSE  4200
# Angular installation if it fails, 

CMD     ["ng", "serve"]

And when i run the app with the command:

docker run -d -p 80:4200 reponame

My build works perfectly and shows me this:

** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **
Compiled successfully.

and when i go to Localhost:4200 it shows that the page is not accessible. i also tried to connect with Ip adress using this commands but same thing.

docker inspect -f ‘{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}’ imagename

i also tried to change different ports because i read in Mac the port 80 might be broken or smth so i tried:

docker run -d -p 4200:4200 appname
docker run -d -p 8080:4200 appname

If anyone can help me, would really greatfull. Thanks !

But _which_ ports? Read https://docs.docker.com/engine/reference/commandline/run/#publish-or-expose-port--p---expose — jonrsharpe, Dec 01 '21 at 09:04
my app port is in 4200 to 80, and i tried to go in localhost:80 same thing — Zemmouri Tarek, Dec 01 '21 at 09:07
You need an `ng serve --host 0.0.0.0` option. If a server ever prints out "listening on localhost:12345` in its startup messages, it won't be reachable from outside its own container. — David Maze, Dec 01 '21 at 11:54
@DavidMaze hmm even if i already specified it in my package.json, i should do it again in my Dockerfile ? — Zemmouri Tarek, Dec 01 '21 at 12:39
You specify `CMD ["ng", "serve"]` in the Dockerfile. It's fine to change that to _e.g._ `CMD ["npm", "run", "start"]` if you have a standard npm script to run the dev server. — David Maze, Dec 01 '21 at 14:15
Yes, i did the changes like you specified but nothing changed always the same result, idk the issue where it would be. — Zemmouri Tarek, Dec 01 '21 at 17:06

Robert-Jan Kuyper · Answer 1 · 2021-12-01T14:12:17.453

0

I assume your app in the container is NOT exposed via the 0.0.0.0 interface.

So in your Angular app, change expose on localhost to 0.0.0.0 instead.

Update your CMD:

CMD ["ng", "serve", "--host", "0.0.0.0"]

Connect from your host system with localhost:80.

edited Dec 01 '21 at 14:12

answered Dec 01 '21 at 10:43

Robert-Jan Kuyper

2,418
12
22

Good idea gona try it, didn't think of that. – Zemmouri Tarek Dec 01 '21 at 11:58
Cool, let me know if it works. – Robert-Jan Kuyper Dec 01 '21 at 12:26
hmm seems not working... – Zemmouri Tarek Dec 01 '21 at 12:32
You changed `ng serve --host 0.0.0.0` in your Dockerfile like @DavidMaze proposed? – Robert-Jan Kuyper Dec 01 '21 at 12:56
Yes just waiting to build and telling you what happened but gona ask you the same question, if already specified it in my package.json, i should do it again in my Dockerfile ? – Zemmouri Tarek Dec 01 '21 at 13:02
Yes you should add the line: `CMD ["ng", "serve", "--host", "0.0.0.0"]` – Robert-Jan Kuyper Dec 01 '21 at 13:43
@Kuyper now i got this error when typing the run command in port 80. An unhandled exception occurred: getaddrinfo ENOTFOUND O.O.O.O See "/tmp/ng-aAAkli/angular-errors.log" for further details. – Zemmouri Tarek Dec 01 '21 at 14:09
You used zero's in the container? And connect with localhost from the host system – Robert-Jan Kuyper Dec 01 '21 at 14:10
Yes i did note zero's on the Dockerfile system, in the CMD["ng", "serve", "--host", "0.0.0.0"], Whzn you say connect with localhost, you mean enter in the Contaner and type the command "ng serve --host 0.0.0.0" ? – Zemmouri Tarek Dec 01 '21 at 14:19

score 0 · Answer 2 · answered Dec 01 '21 at 10:53

0

your port mapping seems incorrect with what you are trying to achieve. -p 80:4200 means that you would use port 80 on your host machine to access the application.

So you should try to access it through http://localhost or http://localhost:80. Even if that is not working, it sometimes happen that your port 80 is already bound to some other application. May be you can try a different port like 8080, 8888 etc instead of 80.

answered Dec 01 '21 at 10:53

Sukhmeet Sethi

616
5
14

Well as i mentionned, it is as you said in http//localhost but if the port was already taken Docker would have told me that it is, no ? – Zemmouri Tarek Dec 01 '21 at 12:33

Can’t acces Docker container on localhost

2 Answers2