Unable to access rocket.chat from localhost after deployment about docker.official.image HOT 8 CLOSED

Hello,
I have the same issue than @jameshowe
I don't have errors in containers
Thanks

from docker.official.image.

On Mac OS X, if you're using docker-machine+boot2docker (the default for Docker Toolbox), you'll need to hit docker-machine ip instead of localhost. If you get access to the Docker for Mac Beta, that restriction goes away and the tooling sets up the necessary forwarding.

I've just verified myself that there isn't a problem with the image (by launching a mongo container, then a rocket.chat linked container, and connecting successfully to the rocket.chat container from my browser).

from docker.official.image.

Can you give the docker command you issue, and also the error you get?

Thanks!

from docker.official.image.

@pierreozoux I'm just running the command from the docs, so in order:

docker run --name db -d mongo --smallfiles
docker run --name rocketchat -p 80:3000 --env ROOT_URL=http://localhost --link db -d rocket.chat

No errors, containers are active just can't access rocket.chat from localhost afterwards as the docs suggest.

from docker.official.image.

It works on Windows. I'll retry on Ubuntu.
Another thing I can't change the configuration "env" (ie --env ROOT_URL=http://hostname:port) after the first start of the container.
I have to stop and remove the mongo container to reset all configurations.

from docker.official.image.

Any updates on this issue ? I also cannot access RocketChat from localhost of from the port forwarding.

from docker.official.image.

Hi,

I feel so confused for digging up this issue, but there are the facts :

• I'm currently experiencing the same strange behavior as above
• It concerns only this image on this system (it works well on other servers, and other images are running without any issue here)
• It looks related to iptables (whereas the rules look correct) as we may encounter these kernel logs while trying to curl http://container.ip.addr:port/ :

  [131513.607649] FIREWALL OUT IN= OUT=docker0 SRC=172.18.0.1 DST=172.18.0.3 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=59805 DF PROTO=TCP SPT=45825 DPT=3000 WINDOW=29200 RES=0x00 SYN URGP=0 
  [131514.604026] FIREWALL OUT IN= OUT=docker0 SRC=172.18.0.1 DST=172.18.0.3 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=59806 DF PROTO=TCP SPT=45825 DPT=3000 WINDOW=29200 RES=0x00 SYN URGP=0 
  [131516.608061] FIREWALL OUT IN= OUT=docker0 SRC=172.18.0.1 DST=172.18.0.3 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=59807 DF PROTO=TCP SPT=45825 DPT=3000 WINDOW=29200 RES=0x00 SYN URGP=0 
  

Any help would be appreciated 👌
I may be able to run some tests if needed !

Thanks !
Bye

EDIT : Our problem looks definitely related to firewall rules, but can't figure why the entries correctly added by Docker are not sufficient to allow a simple connection as above...

EDIT 2 : This was definitely not related to firewall rules, as all other tested containers work well. I think it's rather a IPv6 / IPv4 binding problem when assigned to localhost. Hope it helped someone wandering by the surroundings...

from docker.official.image.

@HorlogeSkynet If you need support, the best is to ask on the community chat.

I'll close this issue for now.

from docker.official.image.